Description of problem: As part of the process of creating a new Machine on GCP, we may set some defaults. When an image is not provided, we set a defult image for the new Machine. The image that we are using is currently from OCP 4.6. It supports ignition v2 but the newer installs are setting up ignition v3 stubs. This breaks the defaulting. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a new GCP cluster on OCP 4.7 2. Modify the machineset to remove the image 3. Scale up Actual results: Machines fail to boot reporting a maximum ignition version of 2.2 Expected results: Machine should be created without issue Additional info:
This was already merged and fixed in 4.8, need to create the appropriate bug chain to backport a fix to 4.7
Verified clusterversion: 4.8.0-0.nightly-2021-04-26-151924 Steps: 1. Create a new GCP cluster on OCP 4.8 2. Modify the machineset to remove the image 3. Scale up Machine could be created without issue. We have a case about default value machineset, we missed this bug because we set the case importce is low, so little chance of being tested. Have set importance to medium.
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.8.2 bug fix and security 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-2021:2438