Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2067

Impact statement: OCPBUGS-13862 operator cloud-controller-manager should not be upgraded between minor versions

    XMLWordPrintable

Details

    • Spike
    • Resolution: Done
    • Blocker
    • None
    • None
    • False
    • None
    • False

    Description

      Which 4.y.z to 4.y'.z' updates increase vulnerability?

      • 4.11 -> 4.12.14 up to 4.12.17
      • 4.12.13 and lower -> 4.12.14 up to 4.12.17

      Versions from 4.12.18 upwards (until full fix) can be also affected in theory but our data suggests this is rare.

      Which types of clusters?

      • all clusters

      What is the impact? Is it serious enough to warrant removing update recommendations?

      CCMO can end up spuriously declaring Upgradeable=False permanently if it goes (even briefly) into Degraded=True. This creates noise in the cluster and blocks further upgrades to 4.13 until the cluster is upgraded to a 4.12 where the issue is resolved. There is no other impact on cluster functionality.

      How involved is remediation?

      Upgrade to later 4.12.z with a fix

      Is this a regression?

      Yes, introduced by https://github.com/openshift/cluster-cloud-controller-manager-operator/pull/239

      Attachments

        Issue Links

          Activity

            People

              mimccune@redhat.com Michael McCune
              afri@afri.cz Petr Muller
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: