Red Hat Bugzilla – Bug 1479838
Wrong matching for LUN disks
Last modified: 2017-09-17 05:24:31 EDT
Description of problem:
In 4.2, the matching of the devices reported form libvirt with those defined in the database was moved from vdsm to the engine. But the logic that was introduced for matching the disks is incomplete. It is done according to the 'path' of the disk (like VDSM used to do), but assumes the following logic: the path must contain the disk id.
However, this logic doesn't hold for LUN disks since their path is composed of "/dev/mapper/<lun_id>". Thus, we need to extend the matching logic for LUN disks, to base on the lun_id instead.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run a VM with a plugged LUN disk
The LUN disk is being unplugged in the engine database
The LUN disk should remain plugged
If the disk is plugged after being unplugged in a previous run of the VM, the VM will start and the LUN disk will remain plugged. So in order to reproduce this bug, we'll need to enforce the devices hash to change by, for example, plugging a NIC.
The fix is supposed to be relatively easy but it needs to be verified with LUN disks so this better gets handled by the storage team.
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.