kiranchavala opened a new issue, #8450: URL: https://github.com/apache/cloudstack/issues/8450
ISSUE TYPE Enhancement/Improvement Request COMPONENT NAME Component: CLOUDSTACK VERSION Cloudstack version 4.18, SUMMARY System vm's volumes should be expunged when a primary storage is set in Maintenance Mode Currently, the system vm volumes are set in destroyed state and have to wait till the storage cleanup thread runs which is 24hrs by default Unless the systemvm's volumes are removed the primary storage can't be removed Steps to reproduce the behavior Example 1. Create a cloudstack enviroment with 2 Primary storages (cluster wide and zone wide) 2. Launch a vm with root disk and data disk ( Both disks are allocated in the cluster wide primary storage) 3. Put the cluster wide storage in Maintainence Mode 5. On putting the Cluster wide storage in Maintainence Mode. The vm goes into stopped state 6. The system vm volumes are recreated in the Zone wide storage 7. The system vm volumes associated with the cluster wide storage are marked in the destroyed state Screenshots   8. Admin user who wants to remove the Cluster wide storage cannot do so unless the system vm volumes are expunged and marked as removed and it depends on the global settings paramters storage.cleanup.interval storage.cleanup.delay storage.cleanup.enabled 9. This doesn't affect the vm disk as they are recreated in another active primary storage Expected behaviour Cloudstack should expunge the systemvm volumes instead of marking them destroyed. As systemvm volumes genrally doesn't contain important data. Or we could have pop up option asking the user if they want to expunge the systemvm volumes immediately when they put a primary storage in Maintenance mode ( some sort of configurable value) -- 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]
