-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.18.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
None
-
Ready to Pick
-
1
-
Customer Escalated, Customer Reported
-
None
-
None
-
None
-
None
-
None
-
None
-
None
New master machines automatically provisioned by the controlplanemachinset are stuck at provisioned.
The vm's deploy in Azure.
Unable to ssh into the machine, can ping it though
The machine-api logs do not indicate any errors
For machine openshift-fsc-r2b7g-master-td2fb-0,
We tried to boot into rescue mode but the serial console in Azure is slow and we were unable to interrupt the grub.
Oddly while rebooting the machine several times trying to interrupt grub the machine transitioned to Running and a new master node was created.
That machine had been stuck at provisioned for over 24 hours
The controlplanemachinset then kicked of the second new master machine, openshift-fsc-r2b7g-master-b95kg-1, and that machine has been stuck at provisioned for several days.
We tried rebooting multiple times but that machine will not transition to Running.
We can not get any logs from that machine, ssh does not work.
In the sosreport for machine openshift-fsc-r2b7g-master-td2fb-0 the journalctl shows th rpm-ostree update starting over and over
Edit from the Cluster Infrastructure Team: please read the comments below for more evidence on this.