monitoring

VirtControllerDown

Meaning

No running virt-controller pod has been detected for 5 minutes.

Impact

Any actions related to virtual machine (VM) lifecycle management fail. This notably includes launching a new virtual machine instance (VMI) or shutting down an existing VMI.

Diagnosis

1. Set the NAMESPACE environment variable:

   $ export NAMESPACE="$(kubectl get kubevirt -A -o custom-columns="":.metadata.namespace)"
   

2. Check the status of the virt-controller deployment:

   $ kubectl get deployment -n $NAMESPACE virt-controller -o yaml
   

3. Review the logs of the virt-controller pod:

   $ kubectl get logs <virt-controller>
   

Mitigation

This alert can have a variety of causes, including the following:

• Node resource exhaustion
• Not enough memory on the cluster
• Nodes are down
• The API server is overloaded. For example, the scheduler might be under a heavy load and therefore not completely available.
• Networking issues

Identify the root cause and fix it, if possible.

If you cannot resolve the issue, see the following resources:

• OKD Help
• #virtualization Slack channel

This site is open source. Improve this page.