The MSTR-SRV pod remains in a PodInitializing status and fails to get to a running status.
Cause
The mstr-srv pod startup failed and stopped.
Solution
Procedure
Check the scripts.log to see the exception that has caused the startup to fail.
Resolve the issue and restart the mstr pod using these instructions:
k scale --replicas=0 deployment mstr-srv -n mstr
Wait for the pod to get fully terminated. Use
k get pods -n mstr |grep mstr-srv
to 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
Note:
A common cause for this issue is incorrect credentials for the mstr administrator.
