Rebooting the UCP Advisor VMs

Unified Compute Platform (UCP) Advisor Administration Guide

Version

4.6.x

Audience

anonymous

Part Number

MK-92UCP119-15

ft:lastEdition

2024-09-24

If you must reboot the UCP Advisor VM for maintenance purposes, perform the following steps to reboot it safely.

Note:

Use the sudo command if you are rebooting the UCP Advisor VM as a non-root user.
If you must shut down the UCP Advisor VM, you can do so safely by running the following command:
```
sudo /opt/ekco/shutdown.sh && sudo shutdown now
```

Using SSH, log on to UCP Advisor VM, and run the following command:
```
sudo /opt/ekco/shutdown.sh && sudo reboot now
```
After the VM is powered on, verify the status of the UCP Advisor pods.
1. Using SSH, log on to the UCP Advisor VM as a ucpadmin user, and then run the following command:
```
kubectl get pods -n ucp
```
2. Verify that the status of the pods are Running or Completed.
3. If the status of the UCP Advisor-kong pod is Init:0/1, then restart the UCP Advisor-kong pod. Enter:
```
kubectl rollout restart -n ucp deployment/ucpadvisor-kong
```
4. Wait for at least one minute, and then verify the status of the pods. Enter:
```
kubectl get pods -n ucp
```
  The status of the pods must be Running or Completed.
In a new browser window, log on to UCP Advisor, and then verify the status of each UCP system.
If the status of a UCP system is Failed, then do one of the following:
- Wait for at least fifteen minutes for the UCP systems to recover.
- Click the Refresh System icon on the Summary tab to refresh the status information.
- Wait for the UCP systems status to become Normal before you perform any UCP-related operations.