hsato03 opened a new pull request, #8649: URL: https://github.com/apache/cloudstack/pull/8649
### Description While listing volumes from a primary storage, volumes from system VMs are not listed, making the primary storage removal process difficult as an exception is thrown if the storage still has active volumes when trying to be deleted. For this reason, logs have been added to the primary storage removal process, informing which undestroyed volumes are associated with the primary storage and which instance they are allocated to if an exception is thrown during the process. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [X] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] build/CI ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [X] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [ ] Minor - [ ] Trivial ### Screenshots (if appropriate): ### How Has This Been Tested? I tried to delete a primary storage with active volumes, then I checked through the logs that all volumes and the VM associated with them were presented. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
