mdesaive commented on issue #5484: URL: https://github.com/apache/cloudstack/issues/5484#issuecomment-924800983
The bug occurs in the following situation: If a volume is created by CloudStack and not ingested from VMWare the path is formed as an UUID. VMWare is actually working with a determined value formed of the VM name and a suffix for counting as volume name. With a live storage migration on VMWare level this volume name is changed from the UUID type to the VM name type and the CloudStack database is not updated. Live storage migrations from VMWare/DRS seem to not change the volume name, when the volume already is stored in the VMWare style. This happens for the volumes, that where ingested with taking before unmanaged VMs into CloudStack management. These are "safe". -- 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]
