loth commented on issue #8901: URL: https://github.com/apache/cloudstack/issues/8901#issuecomment-2073684436
> > @weizhouapache any idea of any further details I should include for this bug? I think 2x secondary storage VMs is largely untested and the root cause of this. > > @loth Is the iso stored on both secondary storages ? Maybe db says it is but actually it isn't. I checked both storage mounts, ISO exists: ``` root@s-27167-VM:/mnt/SecStorage/49e5c7d7-bef0-32c9-8be4-505b3b0b51be# find . -name 2695-2-bec1fada-4469-3072-ab2c-799b0163f1eb.iso ./template/tmpl/2/2695/2695-2-bec1fada-4469-3072-ab2c-799b0163f1eb.iso root@s-27167-VM:/mnt/SecStorage/49e5c7d7-bef0-32c9-8be4-505b3b0b51be# cd .. root@s-27167-VM:/mnt/SecStorage# cd cadb1c27-afcb-314d-a866-e039feae8492/ root@s-27167-VM:/mnt/SecStorage/cadb1c27-afcb-314d-a866-e039feae8492# find . -name 2695-2-bec1fada-4469-3072-ab2c-799b0163f1eb.iso ./template/tmpl/2/2695/2695-2-bec1fada-4469-3072-ab2c-799b0163f1eb.iso ``` Furthermore I think this is more of a bug within cloudstack and how it is generating the location of the ISO. We can see in the output of libvirtd errorlog "/mnt/667dc116-bc57-3e1f-b21a-96babdbcebd4/2695-2-bec1fada-4469-3072-ab2c-799b0163f1eb.iso" is in the domain XML however cloudstack created /mnt/49d099eb-456c-3262-867a-3dd38b623a04 for the VM to mount the ISO from (and the ISO does exist at this mount point) but never updated the XML to use this new mount point. The migration completes but the VM fails to start due to this mount point not existing. So either 2 things needed to happen for this not to error in cloudstack 1. Use the old mount from the XML during migration when spinning up a new nfs mount at the migration destination 2. Update the XML to use the new mount point on the destination (not sure if this is possible) -- 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]
