Provisioning failed on bootstrap due to wrong ignition version used. Version: 4.6, 4.7, master Platform: Azure Please specify: UPI What happened? CI failed at the bootstrap provisioning step: "OS Provisioning for VM 'ci-op-wwdwrwpq-0dfa5-l2dwn-bootstrap' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).\r\n * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ \r\n * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ \r\n * If you are deploying more than 20 Virtual Machines concurrently, consider moving your custom image to shared image gallery. Please refer to https://aka.ms/movetosig for the same." What did you expect to happen? Successful CI, similar to https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/13531/rehearse-13531-pull-ci-openshift-installer-master-e2e-azure-upi/1327275700473827328 How to reproduce it (as minimally and precisely as possible)? Use old bootstrap ignition version (2.2.0 instead of 3.1.0) Anything else we need to know? Succesful CI job ran with WIP for 4.6+: https://github.com/openshift/release/pull/13531/commits/ebacf9f53d8088b2c741108942ee78cd6f76efbf Also removed newline in base64 code to fix maximum length of 87380 characters issue that we had with 4.6+ Would need to add logic for compatibility with earlier versions as well.
Verified with CI passing: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/13531/rehearse-13531-pull-ci-openshift-installer-master-e2e-azure-upi/1327275700473827328 Also saw 4.6 Azure UPI job staring to pass again.
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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/RHSA-2020:5633