Pearl1594 opened a new pull request, #14379:
URL: https://github.com/apache/cloudstack/pull/14379

   ### Description
   
   This PR  fixes: https://github.com/apache/cloudstack/issues/14204
   CLVM/CLVM_NG pools are deliberately kept inactive in libvirt, because LVM is 
driven directly with `vgs`/`lvs`. `ClvmStorageAdaptor` had no 
`deleteStoragePool` of its own, so it used the generic `LibvirtStorageAdaptor` 
version. That version calls `destroy()` on the pool, and libvirt rejects 
`destroy()` on an inactive pool. As a result, a CLVM pool could not be deleted, 
and enabling maintenance on it failed the same way.
   
   With this fix, deleting the pool in CloudStack only removes the CloudStack 
record and the libvirt pool definition on each host. It does not touch the 
volume group or the shared storage behind it. The VG,  the lvmlockd/sanlock 
lockspace are left as they are, as CloudStack does not set any of these up. It 
only checks that the VG exists when the pool is added.
   Tearing them down is the operator's responsibility, for example `vgchange 
--lockstop`, `vgremove`, iSCSI logout and releasing the LUNs.
   
   
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
******************************************************************************* 
-->
   <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
******************************************************************************* 
-->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [X] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [X] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   
   #### How did you try to break this feature and the system with this change?
   
   <!-- see how your change affects other areas of the code, etc. -->
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
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]

Reply via email to