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

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
    • In Progress
    • Bug Fix
    • Hide
      Previously, the installation program checked only the first compute machine pool entry in the install configuration to determine whether to disable the `MachineConfigOperator` (MCO) boot image management. If multiple compute pools were specified (Amazon Web Service (AWS) edge nodes are the only supported scenario), but another compute machine pool had a custom Amazon Machine Image (AMI), the installation program would not disable the MCO boot image management and the custom AMI would be overwritten by the MCO. With this release, the installation program checks all compute machine pool entries and if a custom image is found, the MCO boot image management is disabled. (link:https://issues.redhat.com/browse/OCPBUGS-58060[OCPBUGS-58060])
      Show
      Previously, the installation program checked only the first compute machine pool entry in the install configuration to determine whether to disable the `MachineConfigOperator` (MCO) boot image management. If multiple compute pools were specified (Amazon Web Service (AWS) edge nodes are the only supported scenario), but another compute machine pool had a custom Amazon Machine Image (AMI), the installation program would not disable the MCO boot image management and the custom AMI would be overwritten by the MCO. With this release, the installation program checks all compute machine pool entries and if a custom image is found, the MCO boot image management is disabled. (link: https://issues.redhat.com/browse/OCPBUGS-58060 [ OCPBUGS-58060 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-57803. The following is the description of the original issue:
      —
      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
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Yunfei Jiang Yunfei Jiang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: