Nutanix : HotAdd disk issue with Prism Element

Commvault / Nutanix AHV – HotAdd disk issue with Prism Element 7.5.1.10 (VOL-40301 / VOL-40302)

Hello,

We are currently troubleshooting a Commvault backup issue on a Nutanix AHV environment running Prism Element 7.5.1.10.

The problem occurs during the disk HotAdd / mount operation on the Commvault VSA / Access Node.

The communication with Nutanix Prism on TCP 9440 is working, but after the disk attachment operation, the Linux VSA does not detect the new device.

Relevant Commvault log entries:

CvProcess::system() - udevadm settle --timeout=30
CvProcess::system() - Command completed with rc=0

CDiskMapperLinux::PostAttachDisk() - Pausing to let device node appear

CvSysfs::getNewDeviceName() - No new devices found

CvSysfs::getNewDeviceName() - No new devices found

CDiskMapperLinux::PostAttachDisk() -
No new device found for disk id [<DISK_ID>]

CPrismCentralInfo::MountVM_Disks() -
DiskMapper PostAttach failed for disk [<DISK_ID>]

We then receive an HTTP 404 from the Nutanix Volumes API:

GET
https://<PRISM>:9440/api/volumes/v4.1/config/volume-groups/<VG_ID>/disks/<DISK_ID>

HTTP 404

The disk <DISK_ID> is not associated with the given Volume Group <VG_ID>.

Code: VOL-40302
Error Group: VOLUME_UNKNOWN_ENTITY_ERROR

During the cleanup/detach operation, another error is returned:

DELETE
https://<PRISM>:9440/api/volumes/v4.1/config/volume-groups/<VG_ID>/disks/<DISK_ID>

HTTP 404

Exception occurred as the storage service could not find
the entity Volume Group on entityID <VG_ID>.

Code: VOL-40301
Error Group: VOLUME_UNKNOWN_ENTITY_ERROR

Commvault then reports:

CDiskMapperLinux::DeleteDiskDevice() -
Failed to deduce basename of device []

CPrismCentralInfo::DetachVolumeGroupForVMFromAccessNode() -
Removing [0] hotadded devices from disk mapper - []

So the sequence appears to be:

1. Commvault initiates the disk / Volume Group attachment.

2. udevadm settle completes successfully.

3. The Linux VSA does not see any new disk.

4. Nutanix API returns VOL-40302, indicating that the disk is not associated with the expected Volume Group.

5. During cleanup, Nutanix also returns VOL-40301, indicating that the Volume Group entity cannot be found.

Has anyone already encountered this behavior with Prism Element 7.5.1.10, particularly with Commvault HotAdd / Volume Groups?

I would be interested to know whether this is a known Nutanix issue, an API v4.1 issue, or if there are specific checks/settings to review on the Nutanix side.

Thanks.