SolusVM 2 VM status 'Not exists' in UI

Symptoms 

VM exists and running on a CR but the status in the UI shows:

SVM_ERROR: status 'Not exists' in UI

Cause

Not confirmed a single exact root cause. Suspected issues/connections are: 

• Intermittent Network connections between the nodes and Manager Node
• Libvert handler
• Full CR disk space which leads to Libvert handling issue as well

Resolution

1. Review the worker connections to determine if an increase is necessary.

2. Restart the "libvertd" service:

   # systemctl restart libvertd*

3. Restart the Solus Agent with:

   # systemctl restart solus-agent.service

If above steps do not resolve the case continue with:

1. Subsequently, perform a Backup of the database and reconfigure or restart the Solus containers. 
2. Wait for 5 to 10 minutes
3. Finally, initiate the computer resource upgrade command from the management server