PaulAngus commented on pull request #4283: URL: https://github.com/apache/cloudstack/pull/4283#issuecomment-754821618
Unless I've read the thread incorrectly (and I hope that I have): The aim of the feature is to allow an admin to move a volume from storage pool A (with tag A) to storage pool B (with tag B), despite the fact that the volume's disk offering tag (A) doesn't match the destination tag (B). If this is done, then the DB says that the volume should be in a pool with tag A when it's actually on storage with tag B. Not only is the database then inconsistent with reality, but it will also corrupt the billing of the volume. If I've understood this correctly, then... This could be fixed by making it mandatory to supply a 'correct' new disk offering if the migration would otherwise be blocked by the tag mismatch. The disk offering change should only be made upon successful migration. ---------------------------------------------------------------- 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]
