-
Bug
-
Resolution: Done-Errata
-
Major
-
4.14.0
-
No
-
Proposed
-
False
-
This is a clone of issue OCPBUGS-18754. The following is the description of the original issue:
—
Description of problem:
After control plane release upgrade, in the guest cluster pod 'tuned' uses control plane release image
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. create a cluster in 4.14.0-0.ci-2023-09-06-180503 2. control plane release upgrade to 4.14-2023-09-07-180503 3. in the guest cluster check container image in pod tuned
Actual results:
pod tuned uses control plane release image 4.14-2023-09-07-180503
Expected results:
pod tuned uses release image 4.14.0-0.ci-2023-09-06-180503
Additional info:
After controlplane release upgrade, in control plane namespace, cluster-node-tuning-operator uses control plane release image:
jiezhao-mac:hypershift jiezhao$ oc get pods cluster-node-tuning-operator-6dc549ffdf-jhj2k -n clusters-jie-test -ojsonpath='{.spec.containers[].name}{"\n"}'
cluster-node-tuning-operator
jiezhao-mac:hypershift jiezhao$ oc get pods cluster-node-tuning-operator-6dc549ffdf-jhj2k -n clusters-jie-test -ojsonpath='{.spec.containers[].image}{"\n"}'
registry.ci.openshift.org/ocp/4.14-2023-09-07-180503@sha256:60bd6e2e8db761fb4b3b9d68c1da16bf0371343e3df8e72e12a2502640173990
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHSA-2023:5006
OpenShift Container Platform 4.14.z security update