Pearl1594 opened a new issue, #13747: URL: https://github.com/apache/cloudstack/issues/13747
### problem With CLVM / CLVM-NG, it is required that the volume (LV) be active on the host that eventually starts the VM. This has been taken care of with template based deployments, by ensuring that the volume created from template gets created on the same host as the planned VM destination. This enforcement isn't there for ISOs, which could possibly lead the lv to be created (activated exclusively) on say host1 which the VM being started on host2 - and VM will not be able to start successfully as it can't access the lv. As a workaround, either, one needs to manually deactivate (-an) the lv on host1 and exclusively activate it on host2 (-aey), or a force stop start / restart of agent - would trigger another start attempt, and that will reconcile the lock to the right host. ### versions 4.23.0.0 ### The steps to reproduce the bug 1. Register an ISO 2. Attempt VM deployment from ISO 3. VM may fail because it can access the LV as the activation happened on another host. ### What to do about it? _No response_ -- 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]
