monitoring

VirtApiRESTErrorsBurst

Meaning

For the last 10 minutes or longer, over 80% of the REST calls made to virt-api pods have failed.

Impact

A very high rate of failed REST calls to virt-api might lead to slow response and execution of API calls, and potentially to API calls being completely dismissed.

However, currently running virtual machine workloads are not likely to be affected.

Diagnosis

  1. Set the NAMESPACE environment variable:

    $ export NAMESPACE="$(kubectl get kubevirt -A -o custom-columns="":.metadata.namespace)"
    
  2. Obtain the list of virt-api pods on your deployment:

    $ kubectl -n $NAMESPACE get pods -l kubevirt.io=virt-api
    
  3. Check the virt-api logs for error messages:

    $ kubectl logs -n $NAMESPACE <virt-api>
    
  4. Obtain the details of the virt-api pods:

    $ kubectl describe -n $NAMESPACE <virt-api>
    
  5. Check if any problems occurred with the nodes. For example, they might be in a NotReady state:

    $ kubectl get nodes
    
  6. Check the status of the virt-api deployment:

    $ kubectl -n $NAMESPACE get deploy virt-api -o yaml
    
  7. Obtain the details of the virt-api deployment:

    $ kubectl -n $NAMESPACE describe deploy virt-api
    

Mitigation

Based on the information obtained during the diagnosis procedure, try to identify the root cause and resolve the issue.

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