shwstppr commented on issue #11502: URL: https://github.com/apache/cloudstack/issues/11502#issuecomment-3404537807
@sudo87 @DaanHoogland @SviridoffA From my understanding this issue is seen when: 1. A service offering is created as public (without domain scope) 2. Some VMs are deployed using it 3. Offering is updated to make it restricted to some domain 4. Domain is deleted -> _resulting in the deletion of the offering while there are still VMs using it_ I think we can fix it in tow ways: 1. At the above step 3, prevent restricting offering access to domain(s) when there are already VMs using it outside the domain(s). 2. At the above step 4, instead of deleting the offering, we check if the offering is used outside the domain, and just remove the domain access and make it public again. I would prefer option 1. (I was referring Compute Offerings in my statement but this would be valid for other offerings as well and instead of VM we may have to check network or VPC there) -- 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]
