[OKD-SCOS v4.16] Unable to provision UPI on Openstack(2024.1 Caracal (SLURP)) #2016
Replies: 2 comments
-
Hey, looks like I'm able to deploy OKD 4.16 on Wallaby. I went into detail over on: We need to narrow down what is failing here. So, starting with the bootstrap node, we need to see if the bootstrap process does actually finish. We can do this by checking the Is it possible to attach a |
Beta Was this translation helpful? Give feedback.
-
I have reprovisioned with version Only pods that are failing are the openshift-marketplace ones that already has been flagged in previous bugreport. The new stable release has just been released, so I will be checking that one out asap!
|
Beta Was this translation helpful? Give feedback.
-
Hi,
I have tried multiple nightly builds the last couple of days,all of them as a "fresh install", but all fail the same way.(I have been provisioning okd-fcos stable for 2 years in the UPI-way(w/terraform) like I do now)
Image that has been used to provision nodes with terraform:
fedora-coreos-39.20231101.3.0
Nightly build binary: 4.16.0-0.okd-scos-2024-08-18-110454
Only 1 controller node actually comes up in the cluster, the remaining 2 and 3 worker nodes do not pop up in
oc get csr/nodes
install-config.yaml
:All the worker nodes cannot seem to fetch their ignition file:
The bootstrap node has the following failed service:
Beta Was this translation helpful? Give feedback.
All reactions