[OpenShift Virtualisation] Machine Config Operator (MCP) is in a degraded state

Solution Verified - Updated -

Issue

  • The MCP was stuck and not rolling out due to non-migratable VirtualMachines (VMs) running on the node, preventing the node drain process.
  • Below messages can be seen in the Machine-Config-Controller POD:

    error when evicting pods/"virt_POD_name" -n "namespace_name" (will retry after 5s): admission webhook "virt-launcher-eviction-interceptor.kubevirt.io" denied the request: VMI vmi_name is configured with an eviction strategy but is not live-migratable
    
  • It was found that these VMs had a ReadWriteOnce volume attached, making them non-live-migratable, which led to the issue.

Environment

  • Red Hat OpenShift Container Platform
    • v4.x
  • Red Hat OpenShift Virtualization

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content