Contribute in GitHub:

Debugging the IBM Storage Scale operator

Problem: the operator pod is not successfully deployed

No operator pod appears when running oc get pods -n ibm-spectrum-scale-operator.

Verify that all worker nodes in the Red Hat OpenShift Container Platform cluster are in a Ready state. If not, the operator pod may not have an eligible node to be deployed to.

 # oc get nodes
 NAME                  STATUS      ROLES    AGE   VERSION
 master0.example.com   Ready       master   65d   v1.18.3+6c42de8
 master1.example.com   Ready       master   65d   v1.18.3+6c42de8
 master2.example.com   Ready       master   65d   v1.18.3+6c42de8
 worker0.example.com   NotReady    worker   65d   v1.18.3+6c42de8
 worker1.example.com   NotReady    worker   65d   v1.18.3+6c42de8
 worker2.example.com   NotReady    worker   65d   v1.18.3+6c42de8

Inspect the operator namespace and look for details that may point to any problems.

 oc get deployment -n ibm-spectrum-scale-operator
 oc describe deployment ibm-spectrum-scale-controller-manager -n ibm-spectrum-scale-operator

 oc get replicasets -n ibm-spectrum-scale-operator
 oc describe replicaset <replicaset name> -n ibm-spectrum-scale-operator

Problem: the operator pod shows container restarts

Kubernetes keeps the logs of the current container and the previous container. Take a look at the previous container's logs for any clues using the following command:

oc logs -p <operator pod> -n ibm-spectrum-scale-operator