-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
4.6
-
Low
-
None
-
Rejected
-
Unspecified
-
If docs needed, set a value
Description of problem:
When ClusterResourceOverride operator is updated, the operator deployment is updated with the new image:
$ oc get deployment -n clusterresourceoverride -o yaml | grep "ose-clusterresourceoverride-rhel8@"
value: registry.redhat.io/openshift4/ose-clusterresourceoverride-rhel8@sha256:d522726262bcb298a13dfe1734a221200a98a291ab0499f1325c9e900cfd361a
$ skopeo inspect docker://registry.redhat.io/openshift4/ose-clusterresourceoverride-rhel8@sha256:d522726262bcb298a13dfe1734a221200a98a291ab0499f1325c9e900cfd361a | grep build-date
"build-date": "2021-08-20T21:43:39.984564"
However, the DaemonSet created by ClusterResourceOverride CRO is not updated:
$ oc get ds -n clusterresourceoverride -o yaml | grep registry
image: registry.redhat.io/openshift4/ose-clusterresourceoverride-rhel8@sha256:05dd55dcfcdcc8d8e22597ef4f5f5b46596fa511285a6db1d5a7cc085bcfb38e
$ oc get pods clusterresourceoverride-9p2lh -n clusterresourceoverride -o yaml | grep image
image: registry.redhat.io/openshift4/ose-clusterresourceoverride-rhel8@sha256:05dd55dcfcdcc8d8e22597ef4f5f5b46596fa511285a6db1d5a7cc085bcfb38e
$ skopeo inspect docker://registry.redhat.io/openshift4/ose-clusterresourceoverride-rhel8@sha256:05dd55dcfcdcc8d8e22597ef4f5f5b46596fa511285a6db1d5a7cc085bcfb38e | grep build-date
"build-date": "2020-12-16T07:20:57.662658"
DS image build date is 16/12/20, which is quite old.
Version-Release number of selected component (if applicable):
How reproducible:
Install one old version of ClusterResourceOverride operator, and update it.
- duplicates
-
OCPBUGS-6101 Daemonset is not upgraded after operator upgrade
- Closed