Unable to start a vm which has a iso after vmware storage drs get's triggered in datastore cluster

[kiranchavala]

problem

Unable to start a vm which has a iso after vmware storage drs get's triggered in datastore cluster

versions

Cloudstack version 4.18,4.19,4.20
Vmware 8.0

The steps to reproduce the bug

This issue was also reported before in #7536

1. Have a Cloudstack environment with Vmware 8.0 and datastore cluster and vsphere storage drs enabled

2. Deploy a vm with a iso image

3. Stop the vm

4. Trigger a vsphere storage drs on one of the datastore cluster ( this can done filling up a datastore)

5. Start the vm > vm unable to start

Logs exception

2025-03-26 11:04:13,868 INFO  [c.c.h.v.m.VirtualMachineMO] (DirectAgent-10:ctx-345e2492 10.0.34.33, job-380/job-383, cmd: StartCommand) (logid:a7625e6e) No disk device exactly matching [b41d32cde3184e0ebbe16a706c2aaaa1] was found for volume [b41d32cde3184e0ebbe16a706c2aaaa1.vmdk]. Looking for disk device info against trimmed base name [b41d32cde3184e0ebbe16a706c2aaaa1].
2025-03-26 11:04:13,868 WARN  [c.c.h.v.m.VirtualMachineMO] (DirectAgent-10:ctx-345e2492 10.0.34.33, job-380/job-383, cmd: StartCommand) (logid:a7625e6e) Disk device info lookup for volume [b41d32cde3184e0ebbe16a706c2aaaa1.vmdk] failed as no matching disk device was found.
2025-03-26 11:04:13,869 INFO  [c.c.h.v.u.VmwareHelper] (DirectAgent-10:ctx-345e2492 10.0.34.33, job-380/job-383, cmd: StartCommand) (logid:a7625e6e) [ignored]failed to get message for exception: No such disk device: b41d32cde3184e0ebbe16a706c2aaaa1.vmdk
2025-03-26 11:04:13,869 ERROR [c.c.h.v.r.VmwareResource] (DirectAgent-10:ctx-345e2492 10.0.34.33, job-380/job-383, cmd: StartCommand) (logid:a7625e6e) StartCommand failed due to [Exception: java.lang.Exception
Message: No such disk device: b41d32cde3184e0ebbe16a706c2aaaa1.vmdk
].
java.lang.Exception: No such disk device: b41d32cde3184e0ebbe16a706c2aaaa1.vmdk

6. Check the volumes

mysql> select name,path,pool_id,chain_info from volumes where instance_id=63 \G;
*************************** 1. row ***************************
      name: ROOT-63
      path: b41d32cde3184e0ebbe16a706c2aaaa1
   pool_id: 12
chain_info: {"diskDeviceBusName":"ide0:1","diskChain":["[ids1] i-2-63-VM/b41d32cde3184e0ebbe16a706c2aaaa1.vmdk"]}
1 row in set (0.00 sec)

Complete logs

startlogs.txt

What to do about it?

Cloudstack should start the vm which has a ISO attached after a vsphere storage drs is triggered

[DaanHoogland]

@kiranchavala , would this be an issue with reconsilidation? I.E. waiting untill reconsilidation is done would then again allow start (or migration)

[kiranchavala]

@DaanHoogland Yes As per default behaviour.

Cloudstack reconciles the path and chain info details from the vcentre and starts the vm successfully.

If the vm has an iso Cloudstack fails to reconcile