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

When 2+ MOSCs are applied to a pool, the new MOSC doesn't roll out

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • None
    • None
    • MCO Sprint 275
    • 1
    • In Progress
    • Enhancement
    • Hide
      The name of the `MachineOSConfig` object used with {image-mode-os-on-lower} must now be the same as the machine config pool where you want to deploy the custom layered image. This change prevents using multiple `MachineOSConfig` objects with each machine config pool. (link:https://issues.redhat.com/browse/OCPBUGS-60414[OCPBUGS-60414])
      Show
      The name of the `MachineOSConfig` object used with {image-mode-os-on-lower} must now be the same as the machine config pool where you want to deploy the custom layered image. This change prevents using multiple `MachineOSConfig` objects with each machine config pool. (link: https://issues.redhat.com/browse/OCPBUGS-60414 [ OCPBUGS-60414 ])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-54287. The following is the description of the original issue:
      —
      Expectation is that there will only be 1 MOSC per pool. So add checks in the OCL code path to ensure that there is only one MachineOSConfig for a pool. If a user tries to create multiple, throw an error and do not build or deploy to nodes.

              umohnani Urvashi Mohnani
              umohnani Urvashi Mohnani
              None
              None
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: