Bug 2004568
Summary: | Cluster-version operator does not remove unrecognized volume mounts | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
Component: | Cluster Version Operator | Assignee: | W. Trevor King <wking> |
Status: | CLOSED ERRATA | QA Contact: | Yang Yang <yanyang> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 4.1.z | CC: | aos-bugs, aos-team-ota, cblecker, jialiu, jokerman, lmohanty, mimccune, vrutkovs, wking, yanyang |
Target Milestone: | --- | Keywords: | ServiceDeliveryBlocker, Upgrades |
Target Release: | 4.9.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
If this bug requires documentation, please select an appropriate Doc Type value.
|
Story Points: | --- |
Clone Of: | 2002834 | Environment: | |
Last Closed: | 2021-10-18 17:51:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2002834 | ||
Bug Blocks: |
Comment 1
Yang Yang
2021-09-16 05:10:21 UTC
To prove the procedure in comment#1 is suitable to test the change, I perform the similar test on a 4.8 cluster. # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-09-15-162303 True False 129m Cluster version is 4.8.0-0.nightly-2021-09-15-162303 Inject the volume ca-cert configMap: cluster-autoscaler-operator-ca to the deployment of cluster-autoscaler-operator. # oc get pod NAME READY STATUS RESTARTS AGE cluster-autoscaler-operator-695cfd657-rfss9 2/2 Running 0 155m cluster-autoscaler-operator-766f6648bd-sh2f7 0/2 ContainerCreating 0 10m cluster-baremetal-operator-6468998c6b-tdwpt 2/2 Running 1 155m machine-api-controllers-58cb4f598-hzm4t 7/7 Running 2 148m machine-api-operator-b8cc66c9b-xj7gn 2/2 Running 1 155m # oc get deploy -n openshift-machine-api cluster-autoscaler-operator -o json | jq .spec.template.spec.volumes[] { "configMap": { "defaultMode": 420, "items": [ { "key": "service-ca.crt", "path": "ca-cert.pem" } ], "name": "cluster-autoscaler-operator-ca" }, "name": "ca-cert" } { "name": "cert", "secret": { "defaultMode": 420, "items": [ { "key": "tls.crt", "path": "tls.crt" }, { "key": "tls.key", "path": "tls.key" } ], "secretName": "cluster-autoscaler-operator-cert" } } { "configMap": { "defaultMode": 420, "name": "kube-rbac-proxy-cluster-autoscaler-operator" }, "name": "auth-proxy-config" } The cluster-autoscaler-operator pod gets stuck on the ContainerCreating and the deployment doesn't get the volume removed. Following comment#1 to verify it with 4.9.0-0.nightly-2021-09-16-215330 and passed. Moving it to verified state. 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.9.0 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-2021:3759 |