Description of problem: The machine-controller pod sits in CrashLoopBackoff with this error: https://bugzilla.redhat.com/show_bug.cgi?id=1864352 Version-Release number of selected component (if applicable): 4.5.0-0.nightly-s390x-2020-10-10-030024 (since Thursday essentially) How reproducible: Everytime Steps to Reproduce: 1. Deploy on libvirt with 4.5 nightly builds since Thursday the 8th of October Actual results: Cluster doesn't come up with machine-controller pod failing to start. Expected results: Cluster starts as expected Additional info: This issue is a result of https://bugzilla.redhat.com/show_bug.cgi?id=1864352 - where the other providers were patched but the libvirt provider was not.
Libvirt is not supported in our official doc, just move it to verified. If this still have issues, fell free to reopen it.
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.5.17 bug fix update), 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:4325