mdesaive commented on issue #5484: URL: https://github.com/apache/cloudstack/issues/5484#issuecomment-925684019
We seemed to have found a valid temporary workaround for us: After a volume was attached, we perform a volume live migration with CloudStack. After this had succeeded the volume path in VMWare and the path and chaininfo entries in the CloudStack database are consistently changed to the VMWare naming scheme and afterwards no longer changed through storage migrations triggered from VMWare. -- 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]
