Solution

1. Check the scripts.log to see the exception that has caused the startup to fail.
2. Resolve the issue and restart the mstr pod using these instructions:
   ADDITIONAL INFORMATION: k scale --replicas=0 deployment mstr-srv -n mstr

   Wait for the pod to get fully terminated. Usek get pods -n mstr |grep mstr-srvto verify the pod has terminated, then confirm the volume attachment to the pv has been released. This will not happen until after the pod fully terminates.

   k get pv |grep mstr

   Take a note of the mstr-srv pv name.

   k –request-timeout=15s get volumeattachement |grep <mstr-srv pv name>

   If nothing is returned, continue to next step. Otherwise, escalate to support for further analysis.

   k scale --replicas=1 deployment mstr-srv -n mstr
   ADDITIONAL INFORMATION:

   Note:

   A common cause for this issue is incorrect credentials for the mstr administrator.