Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-57803

MCO manifest for disabling boot image management should consider edge nodes on AWS

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      * Before this update, when you installed {product-title} on {aws-first}, the Machine Config Operator (MCO) for disabling boot image management failed to check edge compute machine pools. When determining whether to disable boot image management, the installer only checked the first compute machine pool entry in the `install-config.yaml`. As a consequence, when you specified multiple compute pools but only the second had a custom Amazon Machine Image (AMI), the installer did not disable MCO boot image management and the MCO could overwrite the custom AMI. With this release, the installation program checks all edge compute machine pools for custom images. As a result, boot image management is disabled when a custom image is specified in any machine pool. (link:https://issues.redhat.com/browse/OCPBUGS-57803[OCPBUGS-57803])
      Show
      * Before this update, when you installed {product-title} on {aws-first}, the Machine Config Operator (MCO) for disabling boot image management failed to check edge compute machine pools. When determining whether to disable boot image management, the installer only checked the first compute machine pool entry in the `install-config.yaml`. As a consequence, when you specified multiple compute pools but only the second had a custom Amazon Machine Image (AMI), the installer did not disable MCO boot image management and the MCO could overwrite the custom AMI. With this release, the installation program checks all edge compute machine pools for custom images. As a result, boot image management is disabled when a custom image is specified in any machine pool. (link: https://issues.redhat.com/browse/OCPBUGS-57803 [ OCPBUGS-57803 ])
    • None
    • None
    • None
    • None

      Description of problem:

          Since https://github.com/openshift/installer/pull/9783, the installer generates an MCO manifest to disable MCO boot image management if a custom boot images are specified. However, the installer did not take into account edge compute machine pool.

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

          4.20.0

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create an install-config with existing VPC where a subnet in Wavelength/Local zone is included.
    2. Define a compute machine pool with name "edge" and specify the custom AMI for that machine pool.
    3. And generate the manifests for check the MCO manifest

      Actual results:

          No MCO manifest

      Expected results:

          MCO manifest for disabling boot image management should be created

      Additional info:

          This line: https://github.com/openshift/installer/blob/b241c4e11500bc2e33db05a7daf45f5ff295065e/pkg/asset/manifests/mco.go#L55 should be extended to check all compute machine pools.

              rh-ee-thvo Thuan Vo
              rh-ee-thvo Thuan Vo
              None
              None
              Yunfei Jiang Yunfei Jiang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: