VM creation fails across different NetApp storage backends in OpenShift Virtualization

Solution Verified - Updated -

Issue

When creating a Virtual Machine from a template, if the source template's disk and the new VM's disk are on different NetApp Trident StorageClasses (representing different physical backends), the new VM's disk is created on the source StorageClass instead of the specified target. The PVC object in OpenShift incorrectly reports that it is using the target StorageClass, while on the physical NetApp backend, the volume is actually created on the source storage backend.

Environment

  • OpenShift Container Platform 4.x
    • OpenShift Virtualization 4.x
  • NetApp Trident CSI with multiple backends configured as separate StorageClasses.

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