Bug 2020107
Summary: | cluster-version-operator: remove runlevel from CVO namespace | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mark Cooper <mcooper> |
Component: | Cluster Version Operator | Assignee: | Over the Air Updates <aos-team-ota> |
Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.10 | CC: | aos-bugs, jiajliu, wking |
Target Milestone: | --- | ||
Target Release: | 4.10.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-03-10 16:24:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mark Cooper
2021-11-04 03:25:14 UTC
I'll attach to your existing PR, where I've asked some questions [1]. Do you have suggestions for how QE should validate this? Is it just "yup, we still install, and it doesn't take much longer without the label [2]"? [1]: https://github.com/openshift/cluster-version-operator/pull/623#issuecomment-960440037 [2]: https://github.com/openshift/enhancements/blob/f6da5f4f7011765da2c928473113bfe913b543a9/CONVENTIONS.md#runlevels +1 I think the "yup, it didn't break anything and it doesn't take a significantly longer time without the label". The only thing I'd add is also a "yup, the operator pod gets an SCC label applied" which in my testing looks like: apiVersion: v1 kind: Pod metadata: annotations: openshift.io/scc: hostaccess creationTimestamp: "2021-11-04T02:30:31Z" generateName: cluster-version-operator-78cd94bc48- ... Reproduced on 4.10.0-0.nightly-2021-11-29-191648 # ./oc get ns openshift-cluster-version -o yaml | grep run-level openshift.io/run-level: "1" # ./oc -n openshift-cluster-version get po cluster-version-operator-68bd8df9d7-rss6q -oyaml|grep scc Verified on 4.10.0-0.nightly-2021-12-03-213835 Fresh installation: # ./oc get ns openshift-cluster-version -o yaml | grep run-level openshift.io/run-level: "" # ./oc -n openshift-cluster-version get po cluster-version-operator-7c48855887-ls9ws -oyaml|grep scc openshift.io/scc: hostaccess Do upgrade from v4.9 to v4.10, before upgrade, # ./oc -n openshift-cluster-version get po cluster-version-operator-7456cb5bff-nl4tl -oyaml|grep scc # ./oc get ns openshift-cluster-version -o yaml | grep run-level openshift.io/run-level: "1" after upgrade, # ./oc get ns openshift-cluster-version -o yaml | grep run-level openshift.io/run-level: "" # ./oc -n openshift-cluster-version get po cluster-version-operator-7f8d6dd84c-pfj79 -oyaml|grep scc openshift.io/scc: hostaccess case added and automated. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 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-2022:0056 |