Inability to relocate attached CNS volumes in vSphere with Tanzu
search cancel

Inability to relocate attached CNS volumes in vSphere with Tanzu

book

Article ID: 313308

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

In vSphere with Tanzu, the VI Admin does not get privileges on the Pod VMs and Tanzu Kubernetes Grid service VMs. If the CNS volume is attached to either a Pod VM or Tanzu Kubernetes Grid service VM, the VI Admin will be unable to relocate the volume.

The operation fails with “Method Invocation Result: NoPermission".


Environment

VMware vCenter Server 8.0.x

Cause

This is by design and product limitation.

Resolution

There is no fix for this issue.

Workaround:

The stateful application in vSphere with Tanzu or Tanzu Kubernetes Grid services needs to be stopped so that the CNS volume goes to a detached state. When the CNS volume is detached, the VI Admin can relocate the volume using Cloud Native Storage UI.