A Historical Reporting pod fails to start

Last Updated : Aug 26, 2020 |
Prolog information

Condition

A Historical Reporting pod fails to start.

Cause

Persistent volume (PV) fails to attach to a node because PV is already attached to another.
PV is a cluster-wide resource that you can use to store data to persists beyond the lifetime of a pod.

Solution

  1. Log in to the Cluster Control Manager (CCM) console as the customer user.
  2. Switch to being the root user by entering the command su.
  3. Restart a pod using the following command:
    ADDITIONAL INFORMATION:
    kubectl delete pod <pod-name>, here pod name is the name of the Historical Reporting pod. For example: kubectl delete pod -n mstr mstr-srv-6954bb949f-trdfg
    Deleting the pod creates a new version of the pod.
  4. To confirm the status of all pods, run the following command:
    ADDITIONAL INFORMATION:
    kubectl get pods
    The pod STATUS column must display as Running and the READY column must display as 1/1.
  5. To get status of the pods in the namespace mstr, run the following command:
    ADDITIONAL INFORMATION:
    kubectl get pods --namespace=mstr