kiranchavala opened a new issue, #10626:
URL: https://github.com/apache/cloudstack/issues/10626

   ### 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 
   
   Before drs 
   
   mysql> select name,path,pool_id,chain_info from volumes where instance_id=60 
\G;
   *************************** 1. row ***************************
         name: ROOT-60
         path: ROOT-60
      pool_id: 12
   chain_info: {"diskDeviceBusName":"ide0:1","diskChain":["[ids1] 
i-2-60-VM/ROOT-60.vmdk","[ids1] 
14145c97164b38fcaf10c7ef6422562c/14145c97164b38fcaf10c7ef6422562c.vmdk"]}
   *************************** 2. row ***************************
         name: DATA-60
         path: 6e5a103aa6a541218edae99ab0883a17
      pool_id: 11
   chain_info: {"diskDeviceBusName":"scsi0:0","diskChain":["[ids2] 
i-2-60-VM/6e5a103aa6a541218edae99ab0883a17.vmdk"]}
   2 rows in set (0.00 sec)
   
   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=60 
\G;
   *************************** 1. row ***************************
         name: ROOT-60
         path: i-2-60-VM_61-000060
      pool_id: 11
   chain_info: {"diskDeviceBusName":"ide0:1","diskChain":["[ids2] 
i-2-60-VM/i-2-60-VM_61-000060.vmdk","[ids2] i-2-60-VM/i-2-60-VM_61.vmdk"]}
   *************************** 2. row ***************************
         name: DATA-60
         path: 6e5a103aa6a541218edae99ab0883a17
      pool_id: 11
   chain_info: {"diskDeviceBusName":"scsi0:0","diskChain":["[ids2] 
i-2-60-VM/6e5a103aa6a541218edae99ab0883a17.vmdk"]}
   2 rows in set (0.00 sec)
   
   
   Complete logs 
   
   
[startlogs.txt](https://github.com/user-attachments/files/19486632/startlogs.txt)
   
   ### What to do about it?
   
   Cloudstack should start the vm which has a ISO attached after a vsphere 
storage drs is triggered 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to