Device manager does not cleans up after disk detaching procedure (fs_lvm)

[kvaps]

Description
After this PR #3131 drive deletion is not working by proper way for the deployed VM.

Eg lvremove operations is always executes on the BRIDGE_LIST nodes, that's not removes device from the current device mapper, and prevent's attaching the new drives on same place.

You will always have device-mapper: create ioctl failed: Device or resource busy error:

[Z0][TM][E]: clone: Command " set -e -o pipefail
[Z0][TM][I]: sudo sync
[Z0][TM][I]: sudo lvscan
[Z0][TM][I]: sudo lvcreate --wipesignatures n -L2048M -n lv-one-7712-2 vg-one-183" failed: device-mapper: create ioctl on vg--one--183-lv--one--7712--2 LVM-4ueRZkrJZfBxe7CAblNFEesMi0SjesPLhTwIQHirn48QrtRC81zLJU8uUTUvHWxz failed: Device or resource busy
[Z0][TM][I]: Failed to activate new LV.
[Z0][TM][E]: Error creating LV named lv-one-7712-2
[Z0][TM][E]: Error executing image transfer script: Error creating LV named lv-one-7712-2
sudo lvcreate --wipesignatures n -L512M -n lv-one-7712-2 vg-one-183" failed: device-mapper: create ioctl on vg--one--183-lv--one--7712--2 LVM-4ueRZkrJZfBxe7CAblNFEesMi0SjesPLIl6yDgmkKbXrFnZQ7y1QETJqEEJ5y9kc failed: Device or resource busy

I wrote about it #3201 (comment)

To Reproduce

• Set BRIDGE_LIST for system fs_lvm datastore
• Create new VM on the non BRIDGE_LIST node
• Detach the drive
• Attach new one

Expected behavior
Attached drive

Details

• Affected Component: Storage
• Hypervisor: KVM
• Version: 5.8.1

Additional context
Add any other context about the problem here.

Progress Status

• Branch created
• Code committed to development branch
• Testing - QA
• Documentation
• Release notes - resolved issues, compatibility, known issues
• Code committed to upstream release/hotfix branches
• Documentation committed to upstream release/hotfix branches

[kvaps]

Solved this by commit a075eb9 in PR #3201