The fix wasn't built into 4.5.31 images.
F
Created attachment 1755170 [details] Logging Upgrade failed from 4.4 to 4.5 The cluster-logging couldn't be upgraded to 4.5 $ oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterlogging.4.5.0-202102032236.p0 Cluster Logging 4.5.0-202102032236.p0 clusterlogging.4.4.0-202102021535.p0 Succeeded elasticsearch-operator.4.5.0-202102041225.p0 Elasticsearch Operator 4.5.0-202102041225.p0 elasticsearch-operator.4.4.0-202102021535.p0 Succeeded $ oc get pods NAME READY STATUS RESTARTS AGE cluster-logging-operator-788bc9749-7zbc2 1/1 Running 0 9m18s curator-1612495800-8vmct 0/1 Completed 0 13m curator-1612496400-n2mgv 0/1 Error 0 3m26s elasticsearch-cdm-e3nmr844-1-744596fbd9-clpwq 2/2 Running 0 14m elasticsearch-cdm-e3nmr844-2-578d7dbb9-npvm5 2/2 Running 0 14m elasticsearch-cdm-e3nmr844-3-746666c444-djlzv 2/2 Running 0 14m fluentd-9hmz6 1/1 Running 0 14m fluentd-md9p9 1/1 Running 0 14m fluentd-np7wx 1/1 Running 0 14m fluentd-rrwn9 1/1 Running 0 14m fluentd-rsh5b 1/1 Running 0 14m fluentd-vtkv5 0/1 Init:CrashLoopBackOff 6 8m51s kibana-5495cfd8bd-khvnx 2/2 Running 0 8m49s $oc logs $ oc logs fluentd-vtkv5 Error from server (BadRequest): container "fluentd" in pod "fluentd-vtkv5" is waiting to start: PodInitializing
Please ignore commens 6. It turn of to be a partial upgrade status. The CLO was updated while EO is still 4.4
Verified on clusterlogging.4.5.0-202102032236.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.5.31 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-2021:0315