Use the following guidelines and suggested steps to help resolve issues when rebooting the UCP Advisor VM.
- Condition:
- UCP Advisor becomes inaccessible after rebooting the UCP Advisor VM, even though the pods are still running.
- What it Means:
- UCP Advisor is not accessible after rebooting the VM.
- Corrective Action:
- On the UCP Advisor VM, verify that the UCP Advisor-kong pod status is in the Normal state. Enter:
kubectl get pods -n ucp
If the UCP Advisor-kong pod is in the Init 0/1 state, then restart the UCP Advisor-kong pod. Enter:kubectl rollout restart deployment ucpadvisor-kong -n ucp