GutoVeronezi commented on issue #8034: URL: https://github.com/apache/cloudstack/issues/8034#issuecomment-1931935624
> @GutoVeronezi , I saw this mitigation procedures from the release note, when we have hundreds VM affected by this linked snapshot issue, I'd like to ask rather than converting them, shall we just left it as it and just told the user do not delete any affected template instead. Any potential issue if we just keep it as is and proceed the 4.19 upgrade? Hello @levindecaro If you will keep the snapshots as they are (so they get replaced over time), you have to bear in mind 2 points: - not delete the template (as you already proposed); - and, when reverting a snapshot, the host where the VM is running must have access to the primary storage referenced in the snapshots's backing store[^cluster-wide]. This is also valid for deploying VMs from templates created from snapshots [^cluster-wide]. With that, your snapshots should work fine until they get replaced with new and consistent snapshots (on 4.19). If you have any other doubt, just ping me. [^cluster-wide]: for instance, if you have a snapshot of a volume in a cluster primary storage, create a template from it, and try to deploy it in another cluster, you will face errors. -- 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]
