rafaelweingartner commented on pull request #4283: URL: https://github.com/apache/cloudstack/pull/4283#issuecomment-754130004
One alternative would then be to forbid the override placement. And then, we allow changing the target storage pool, as long as the new disk offering matches it (or the current disk offering, if there is no new disk offering). What do you think? Then, the DB would always be consistent with the storage where the volume resides. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
