Description of problem: When performing a libvirt IPI install of OpenShift 4.3, the provider does not set a phase. Version-Release number of selected component (if applicable): 4.3.z How reproducible: Always Steps to Reproduce: 1. Perform libvirt IPI installer 2. oc get machines -n openshift-machine-api Actual results: NAME PHASE TYPE REGION ZONE AGE test-ocp-9nngh-master-0 2d20h test-ocp-9nngh-master-1 2d20h test-ocp-9nngh-master-2 2d20h test-ocp-9nngh-worker-0-g2vjg 2d20h test-ocp-9nngh-worker-0-jt779 2d20h Expected results: Phase is set by the machine controller. Additional info: Upon scaling machineset replicas, the cluster begins firing MachineWithNoRunningPhase alerts which never resolve. These alerts do not seem to trigger without scaling machinesets.
Created attachment 1685385 [details] must-gather
Based on a slack conversation with the cloud team, it looked like the libvirt actuator is not using the latest version of the machine controller which could be causing this.
Hi zeenix, I'm tagging this with upcomingSprint. Please feel free to drop it if you're planning to tackle this sooner.
should be fixed by: https://github.com/openshift/cluster-api-provider-libvirt/pull/198. Was able to test the changes and I see phase set.
Thanks, I think this is verified based on the above comments.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196