Description of problem: The fluentd-init container image isn't updated to the new image during the upgrade. Version-Release number of selected component (if applicable): clusterlogging.4.5.0-202008100413.p0 -> clusterlogging.4.6.0-202008102017.p0 How Reproducible: Always Steps to Reproduce: 1) Deploy cluster logging 4.5 2) Deploy 4.6 catalog source service 3) Upgrade CLO and EO to 4.6 4) Check the fluentd-init container image Actual Result: The fluentd-init image is a 4.5 image "quay.io/openshift-qe-optional-operators/ose-logging-fluentd:xxxx" $ oc get ds fluentd -o json | jq '.spec.template.spec' "containers": [ { ...... ...... "image": "registry.redhat.io/openshift4/ose-logging-fluentd@sha256:1656abbfa048c6248feb2ea0ce4b5a6b0ade00e88700643a0019285481341ea4", "imagePullPolicy": "IfNotPresent", "name": "fluentd", ...... ...... } ], "dnsPolicy": "ClusterFirst", "initContainers": [ { "command": [ "./wait_for_es_version.sh", "6", "https://elasticsearch.openshift-logging.svc:9200" ], "image": "quay.io/openshift-qe-optional-operators/ose-logging-fluentd@sha256:1e600cb3f3bab64f1736e1fd7761e3d97b4f2a52ed6aa92c97f26747f9629ac8", "imagePullPolicy": "IfNotPresent", "name": "fluentd-init" .......... ......... } ] Expected Result: he fluentd-init image should be registry.redhat.io/openshift4/ose-logging-fluentd@xxxxxx
Created attachment 1711088 [details] clo pod log
Moving to UpcomingSprint for future evaluation
Verified on clusterlogging.4.6.0-202008262209.p0
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.6.1 extras 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-2020:4198