mwaag commented on issue #13249:
URL: https://github.com/apache/cloudstack/issues/13249#issuecomment-5143556284

   Hi there, hi @DaanHoogland 
   
   we run in this exact problem with cloudstack 4.20.3.0 and Vsphere 8.0.3 
(0700).
   
   Our insights on this so far:
   
   - Cloudstack 4.20.3.0 creates data-disk with VMWare 
VirtualDiskStorageObjectManager
   - this creates a so called 'first class disk', the descriptor file contains 
ddb.fcd.-entries.
   - when attached, cloudstack manages the disk as conventional vmdk and copies 
descriptor and -flat.vmdk into directory of target-vm
   - cloudstack then calls updateVmdkAdapter() to change controller-type in 
copied vmdk-descriptor-file
   - therefore cloudstack tries to download descriptor-file via vsphere file 
browser http://vcenter.url/folder/....vmdk
   - vcenter 8.0.3 notices the ddb.fcd.-entries, thinks its still an first 
class disk and tries to manage through VStorageObject
   - but in target-dir doesn't exist a VStorageObject, vCenter reports 
vim.fault.NotFound and delivers HTTP 500
   - cloudstack cancels attach-action
   
   We created a request to shapeblue (ticket 7160) just today as this will keep 
us from migrating to vmware 8 (which is comming more urgent since the newest 
vmsa: 
[VMSA-2026-0006](https://app.sw.broadcom.com/e/er?utm_campaign=VCF_FY26_VCF_[VMSA-2026-0006](https://app.sw.broadcom.com/e/er?utm_campaign=VCF_FY26_VCF_VMSA-2026-0006_MKT_CM_6366&utm_content=VCF_FY26_VCF_VMSA-2026-0006_6366_SecurityAlert_MKT_TRANS_EM_12661&utm_medium=email&utm_source=eloqua&s=3805888&lid=14177&elqTrackId=5553B7F840A600113BAEECE9E93F8772&elq=acece55a4e3f4f70a23887c3ee75dcc2&elqaid=12661&elqat=1&elqak=8AF5A65488C34F212FD12185660609AA05B6BC7DBD2971371810324C66638F1D42AE)_MKT_CM_6366&utm_content=VCF_FY26_VCF_VMSA-2026-0006_6366_SecurityAlert_MKT_TRANS_EM_12661&utm_medium=email&utm_source=eloqua&s=3805888&lid=14177&elqTrackId=5553B7F840A600113BAEECE9E93F8772&elq=acece55a4e3f4f70a23887c3ee75dcc2&elqaid=12661&elqat=1&elqak=8AF5A65488C34F212FD12185660609AA05B6BC7DBD2971371810324C66638F1D42AE)
 ) and are currently wo
 rking internally on a patch for 4.20.3.0 (which looks promising so far) and 
after some more testing planing to open a PR for it for more / better review.


-- 
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