Description of problem:

OpenShift 4.19 introduced default boot-image management for AWS & GCP. The problem is that if users set a custom boot image, such as a marketplace image or otherwise custom image, the MCO will overwrite the user-specified image with the managed one (at which point the image is overwritten, TBD).

Losing the image would be an issue for marketplace images as we would stop billing for those or custom images may lose required assets, such as CAs, which could result in failures.

Version-Release number of selected component (if applicable):

    4.19.0

How reproducible:

    Always

Steps to Reproduce:

    1. Set custom boot image in either default, control plane or compute machine pool
      a. aws: platform.aws.amiID
      b. gcp: platform.gcp.osImage
    2. Perform installation
    3. Check machineset for updated bootimage
    

Actual results:

    custom boot image is overwritten in machinesets

Expected results:

    custom boot image is maintained in machineset

Additional info:

slack xref (source of this bug): https://redhat-internal.slack.com/archives/C68TNFWA2/p1749651650860599 The fix for this issue is discussed in this thread. We just need to agree on the fix.

rhn-support-sdodson pointed out that a minimum boot image will be enforced in the cluster, so if we decide that users will be on the hook for managing boot images when specifying custom images, we will need to document the need to update.