Verified with clusterlogging.4.4.0-202003021617 $ oc get cm NAME DATA AGE cluster-logging-operator-lock 0 10m curator 3 51s elasticsearch 3 53s fluentd 3 51s fluentd-trusted-ca-bundle 1 51s kibana-trusted-ca-bundle 1 53s sharing-config 2 53s $ oc get pod NAME READY STATUS RESTARTS AGE cluster-logging-operator-759d46d79c-zvx5b 1/1 Running 0 18m elasticsearch-cdm-c6j7etjj-1-6c47698995-8jsfn 2/2 Running 0 8m23s fluentd-9tsdk 1/1 Running 0 8m20s fluentd-gn2h4 1/1 Running 0 8m20s fluentd-jbbjw 1/1 Running 0 8m20s fluentd-sgvxk 1/1 Running 0 8m20s fluentd-tmjp7 1/1 Running 0 8m20s fluentd-vt28n 1/1 Running 0 8m20s kibana-6985f8cb5c-7fm7x 2/2 Running 0 8m22s
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, 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:0581