Description of problem: Improve block SD teardown and cleanup of LVs and VG mappings. As per discussion under https://gerrit.ovirt.org/#/c/109836/ the flow should look like this: * deactivate vg * log warnings from this command or the error message if it fails * maybe log a warning about lvs that are still active in this vg - "dmsetup status" can be good way to find them. * if there are active (but not open) lvs after this call, we can open LVM bug, I think lvm should clean up in all case * if there are cases when lvm does not clean up we can use "dmesetup remove" with a warning since this is not expected
Vojtech, can you please provide a clear verification flow? The flow you mentioned is unclear.
(In reply to Evelina Shames from comment #3) > Vojtech, can you please provide a clear verification flow? > The flow you mentioned is unclear. 1. create block SD 2. check that LV on this SD are active 3. put SD into maintenance 4. check all LVs on this SD and VG corresponding to this SD are deactivated
(In reply to Vojtech Juranek from comment #4) > (In reply to Evelina Shames from comment #3) > > Vojtech, can you please provide a clear verification flow? > > The flow you mentioned is unclear. > > 1. create block SD > 2. check that LV on this SD are active > 3. put SD into maintenance > 4. check all LVs on this SD and VG corresponding to this SD are deactivated Thanks! Verified with the following flow on rhv-4.4.3-8: 1. Create block SD 2. Connect to its host 3. Run lvdisplay 4. Search for /dev/<sd_id> and under 'LV Status' check that it is 'available' 5. Put SD into maintenance 6. Run lvdisplay again 7. This time search for /dev/<sd_id> and under 'LV Status' check that it is 'NOT available' Vojtech, is that what you meant?
(In reply to Evelina Shames from comment #5) > (In reply to Vojtech Juranek from comment #4) > > (In reply to Evelina Shames from comment #3) > > > Vojtech, can you please provide a clear verification flow? > > > The flow you mentioned is unclear. > > > > 1. create block SD > > 2. check that LV on this SD are active > > 3. put SD into maintenance > > 4. check all LVs on this SD and VG corresponding to this SD are deactivated > > Thanks! > > Verified with the following flow on rhv-4.4.3-8: > 1. Create block SD > 2. Connect to its host > 3. Run lvdisplay > 4. Search for /dev/<sd_id> and under 'LV Status' check that it is 'available' > 5. Put SD into maintenance > 6. Run lvdisplay again > 7. This time search for /dev/<sd_id> and under 'LV Status' check that it is > 'NOT available' > > Vojtech, is that what you meant? yes
(In reply to Vojtech Juranek from comment #6) > (In reply to Evelina Shames from comment #5) > > (In reply to Vojtech Juranek from comment #4) > > > (In reply to Evelina Shames from comment #3) > > > > Vojtech, can you please provide a clear verification flow? > > > > The flow you mentioned is unclear. > > > > > > 1. create block SD > > > 2. check that LV on this SD are active > > > 3. put SD into maintenance > > > 4. check all LVs on this SD and VG corresponding to this SD are deactivated > > > > Thanks! > > > > Verified with the following flow on rhv-4.4.3-8: > > 1. Create block SD > > 2. Connect to its host > > 3. Run lvdisplay > > 4. Search for /dev/<sd_id> and under 'LV Status' check that it is 'available' > > 5. Put SD into maintenance > > 6. Run lvdisplay again > > 7. This time search for /dev/<sd_id> and under 'LV Status' check that it is > > 'NOT available' > > > > Vojtech, is that what you meant? > > yes Great, moving to 'Verified'.
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.