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

Born in 4.1 and 4.2 clusters have 'openshift.io/run-level: 1' uncleared


    • Moderate
    • False
    • Hide



      $ git --no-pager log -1 --oneline 75f34c7a944e20904d48949a3bd9b1f9496252c0 
      75f34c7a manifests: Remove run-level, insights operator does not need it

      Removed the openshift.io/run-level annotation from the manifest, but as described in OTA-330, removing the label doesn't clear it from existing clusters. To remove the run-level effect, the manifest should set it to an empty string, as seen here. Checking exposure:

      $ git --no-pager grep openshift.io/run-level origin/release-4.2 -- manifests
      origin/release-4.2:manifests/02-namespace.yaml:    openshift.io/run-level: "1"
      $ git --no-pager grep openshift.io/run-level origin/release-4.3 -- manifests
      ...no hits...

      So clusters born in 4.1 and 4.2 probably still have the old run-level hanging around. Clusters born in 4.3 and later will be clean.

      This can cause trouble updating to 4.11, with updates to 4.11.3 sticking with:

      container has runAsNonRoot and image will run as root (pod: "insights-operator-746754b75c-bx2r9_openshift-insights(53968a4e-53f7-4093-94ff-ac8d3dfbae07)", container: insights-operator)

      This bit a number of other operators in 4.11 too, but we missed the insights operator when cleaning things up.

            tremes1@redhat.com Tomas Remes
            trking W. Trevor King
            Joao Bastos Fula Joao Bastos Fula
            0 Vote for this issue
            7 Start watching this issue