Created attachment 1845774 [details] correct output Document URL: https://docs.openshift.com/container-platform/4.9/logging/cluster-logging-deploying.html#cluster-logging-deploy-console_cluster-logging-deploying https://docs.openshift.com/container-platform/4.9/logging/cluster-logging-deploying.html#cluster-logging-deploy-cli_cluster-logging-deploying Section Number and Name: 4. Verify the install: b. Select the openshift-logging project. 6. Verify the installation by listing the pods in the openshift-logging project Describe the issue: In the text output (GUI mode) and image (CLI mode) is showing the pod is named "fluentd" but currently (cluster version 4.9), the correct name of pod is "collector". Suggestions for improvement: Change the "oc get pod -n openshift-logging" output to not generate doubts. Additional information: [root@localhost ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0 True False 10d Cluster version is 4.9.0 [root@localhost ~]# oc project Using project "openshift-logging" on server "https://api.ttoledo.nasatam.support:6443". [root@localhost ~]# oc get pods NAME READY STATUS RESTARTS AGE cluster-logging-operator-744c5bdb78-rhzqg 1/1 Running 0 71m collector-5tj7h 2/2 Running 0 61m collector-hzkmn 2/2 Running 0 61m collector-pqxf9 2/2 Running 0 61m collector-pwb7m 2/2 Running 0 61m collector-vq4mr 2/2 Running 0 61m collector-wdmlh 2/2 Running 0 61m collector-x68gz 2/2 Running 0 61m elasticsearch-cdm-8zo6ml19-1-845dd58b8b-cmw2l 2/2 Running 0 57m elasticsearch-cdm-8zo6ml19-2-5bb7959d6f-ccpv9 2/2 Running 0 59m elasticsearch-cdm-8zo6ml19-3-6fc9bd6f48-z2vb6 2/2 Running 0 59m elasticsearch-im-app-27319725--1-g2d9f 0/1 Completed 0 3m34s elasticsearch-im-audit-27319725--1-rv6w2 0/1 Completed 0 3m34s elasticsearch-im-infra-27319725--1-brhzb 0/1 Completed 0 3m34s kibana-6f4766fcf6-jzn5f 2/2 Running 0 62m
All open BZs in this project will be migrated to Jira in the near future. Because this BZ has already been cloned into Jira, I am closing it now to reduce the number of duplicate Jiras. This bug will be triaged for future work on the Jira issue that is shown in the Links section.