Checking the status of your cluster

You can use dashboards and commands to check the status of your OpenShift Container Platform (OCP) cluster.

Check the overall status in the dashboard

To see the overall status of the OCP cluster, go to 
https://console-openshift-console.apps.<mycluster.mydomain.com>/dashboards
Replace <mycluster.mydomain.com> with your own cluster name.
  • In Cluster inventory, you can check the status of your nodes, pods, storage classes, and persistent volume claims (PVCs).
  • In Status, you can check the status of the cluster, control plane, and operators. You can see the OCP cluster alerts.
  • In Cluster utilization, you can check the status and available resources of CPU, memory, filesystem, network transfer, and pod count.
  • In Activity, you can see the latest OCP cluster events. OpenShift uses events to record information about the life cycle of the cluster and show information about OpenShift components in a unified way. Events are helpful for troubleshooting.

Check the status of resources

You can check all the resources in the dashboard. For example, if you installed in the namespace cp4ba, you can go to 
https://console-openshift-console.apps.<mycluster.mydomain.com>.com/k8s/cluster/projects/cp4ba
In Inventory, you can monitor all the resources, including deployments, StatefulSets, pods, PVCs, and services. Click any link to view the details of the resource. For example, click pods to go to the Details page and watch all the pods in the cp4ba namespace.

Check the status of CPU and memory usage

To show the percentage and absolute value of the CPU and memory usage on each node, run the command 
oc adm top nodes
The output of this command looks like the following example:
Name CPU(cores) CPU% Memory(bytes) Memory%
master0.mycluster.mydomain.com 1280m 17% 8662Mi 59%
master1.mycluster.mydomain.com 1184m 15% 7007Mi 48%
master2.mycluster.mydomain.com 1415m 18% 8710Mi 59%
worker0.mycluster.mydomain.com 1458m 19% 13316Mi 91%
worker1.mycluster.mydomain.com 2756m 36% 9984Mi 68%
worker2.mycluster.mydomain.com 1072m 14% 9854Mi 67%

Check the status of the pods

To see the pods that you deployed in the cp4ba namespace, run
oc get pod -n cp4ba
For example, if you run 
oc get pod -n cp4ba \|grep -E "\-baw-.*"
You might see results like the following example. These results indicate a successful deployment.
NAME READY STATUS RESTARTS AGE
icp4adeploy-instance1-baw-case-init-job--1-7mvx6 0/1 Completed 0 4h34m
icp4adeploy-instance1-baw-content-init-job--1-9ws28 0/1 Completed 0 4h34m
icp4adeploy-instance1-baw-db-init-job--1-mkglw 0/1 Completed 0 4h34m
icp4adeploy-instance1-baw-db-init-job-pfs--1-rrf6n 0/1 Completed 0 4h34m
icp4adeploy-instance1-baw-jms-0 1/1 Running 0 4h32m
icp4adeploy-instance1-baw-ltpa--1-xz24v 0/1 Completed 0 4h34m
icp4adeploy-instance1-baw-server-0 1/1 Running 0 4h26m
icp4adeploy-instance1-baw-workplace-job--1-hjrtx 0/1 Completed 0 4h33m
The READY column gives a result like 1/1 or 2/2 if the pod is running.
The following table shows the common states in the STATUS column and what they mean.
Status Meaning
Running Pod deployed successfully
ImagePullBackOff Retrying to pull the image
ErrImagePull Error pulling the image
PodInitializing Pod is initializing
ContainerCreating Container is being created
CrashLoopBackOff Container exited and kubelet is restarting it
CreateContainerError Failed to create container
Completed Job completed successfully
Error| Pod failed to initialize
To show the information for just one pod, for example icp4adeploy-instance1-baw-server-0, run
oc describe pod icp4adeploy-instance1-baw-server-0
To see the Workflow pod log, run
oc logs icp4adeploy-instance1-baw-server-0
To see the logs for all Workflow pods, connect to the baw containers inside your cluster by running
oc exec -it demo-instance1-baw-server-0 -- bash
Then, go to the /logs/application/ folder to find all the Workflow logs.
To download all the Workflow logs, run
oc -c workflow-server cp demo-instance1-baw-server-0:logs/application/ .

Check the status of events

To see event information, run 
oc get events
The OpenShift namespace can capture the following events
  • Pod creation and deletion
  • Nodes scheduled by pod
  • Status of master and worker nodes
Events are usually used for troubleshooting to obtain high-level information about faults and problems in the cluster. You can then use log files and other oc commands to further locate the problem.