Bug 2032125 - Cluster-version operator does not remove unrecognized volume mounts
Summary: Cluster-version operator does not remove unrecognized volume mounts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.z
Assignee: W. Trevor King
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On: 2026560
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-14 05:55 UTC by OpenShift BugZilla Robot
Modified: 2022-03-29 07:16 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-29 07:16:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-version-operator pull 715 0 None open [release-4.9] Bug 2032125: lib/resourcemerge/core: Merge volumeMounts by mountPath 2021-12-14 05:55:16 UTC
Red Hat Product Errata RHBA-2022:1022 0 None None None 2022-03-29 07:16:38 UTC

Comment 4 sunzhaohua 2022-03-22 10:20:46 UTC
Verified
clusterversion: 4.9.0-0.nightly-2022-03-21-144414
$ oc patch deploy cluster-autoscaler-operator --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/1/volumeMounts/0","value":{"mountPath":"etc/cluster-autoscaler-operator/tls/service-ca","name":"cert","readOnly":true}}]'
deployment.apps/cluster-autoscaler-operator patched
        
After update, check autoscaler pod and deployment, work as expected.
$ oc get po                                                                                                      [18:17:21]
NAME                                           READY   STATUS                 RESTARTS   AGE
cluster-autoscaler-operator-64795b9446-p8dvd   2/2     Running                0          6h54m
cluster-autoscaler-operator-d6b8df484-wm6wk    1/2     CreateContainerError   0          78s
cluster-baremetal-operator-ffdbdf56f-zpxgf     2/2     Running                0          6h54m
machine-api-controllers-944cfbdcc-mxx95        7/7     Running                0          6h51m
machine-api-operator-75cbcfb9b8-tftvr          2/2     Running                0          6h54m
 $ oc get po                                                                                                      [18:17:58]
NAME                                           READY   STATUS        RESTARTS   AGE
cluster-autoscaler-operator-64795b9446-p8dvd   2/2     Running       0          6h55m
cluster-autoscaler-operator-d6b8df484-wm6wk    1/2     Terminating   0          2m15s
cluster-baremetal-operator-ffdbdf56f-zpxgf     2/2     Running       0          6h55m
machine-api-controllers-944cfbdcc-mxx95        7/7     Running       0          6h52m
machine-api-operator-75cbcfb9b8-tftvr          2/2     Running       0          6h55m
$ oc get po                                                                                                      [18:18:57]
NAME                                           READY   STATUS    RESTARTS   AGE
cluster-autoscaler-operator-64795b9446-p8dvd   2/2     Running   0          6h55m
cluster-baremetal-operator-ffdbdf56f-zpxgf     2/2     Running   0          6h55m
machine-api-controllers-944cfbdcc-mxx95        7/7     Running   0          6h52m
machine-api-operator-75cbcfb9b8-tftvr          2/2     Running   0          6h55m

$ oc get deployment.apps/cluster-autoscaler-operator -n openshift-machine-api -ojson|jq .spec.template.spec.containers[1].volumeMounts
[
  {
    "mountPath": "/etc/cluster-autoscaler-operator/tls",
    "name": "cert",
    "readOnly": true
  }
]

Comment 7 errata-xmlrpc 2022-03-29 07:16:22 UTC
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 (OpenShift Container Platform 4.9.26 bug fix 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/RHBA-2022:1022


Note You need to log in before you can comment on or make changes to this bug.