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

The MCO does not properly degrade when pools are failing to render a new config

XMLWordPrintable

    • Moderate
    • None
    • 2
    • MCO Sprint 260
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      When machineconfig fails to generate, we set upgradeable=false and degrade pools. The expectation is that the CO would also degrade after some time (normally 30 minutes) since master pool is degraded, but that doesn't seem to be happening. Based on our initial investigation, the event/degrade is happening but it seems to be being cleared.

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

          4.18

      How reproducible:

          Should be always

      Steps to Reproduce:

          1. Apply a wrong config, such as a bad image.config object:
spec:
  registrySources:
    allowedRegistries:
    - test.reg
    blockedRegistries:
    - blocked.reg
    
    2. upgrade the cluster or roll out a new MCO pod
    3. observe that pools are degraded but the CO isn't

      Actual results:

      Expected results:

      Additional info:

            [OCPBUGS-42546] The MCO does not properly degrade when pools are failing to render a new config

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Important: OpenShift Container Platform 4.18.1 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-2024:6122

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Important: OpenShift Container Platform 4.18.1 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-2024:6122

            Prachiti Talgulkar added a comment -

            Fix included in build 4.18.0-0.nightly-2024-10-02-125103 and pre-merge verified

            Moving to VERIFIED.

            Prachiti Talgulkar added a comment - Fix included in build 4.18.0-0.nightly-2024-10-02-125103 and pre-merge verified Moving to VERIFIED.

            OpenShift Jira Bot added a comment -

            Hi djoshy,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi djoshy , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            Sergio Regidor de la Rosa added a comment -

            Pre-merge verified in: https://github.com/openshift/machine-config-operator/pull/4617

            Sergio Regidor de la Rosa added a comment - Pre-merge verified in: https://github.com/openshift/machine-config-operator/pull/4617

              djoshy David Joshy
              jerzhang@redhat.com Yu Qi Zhang
              Sergio Regidor de la Rosa Sergio Regidor de la Rosa
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: