Red Hat Bugzilla – Bug 981962
[vdsm] wrong disk state report by engine in case of a failure in disk hotplug/hotunplug
Last modified: 2016-02-10 12:46:04 EST
Created attachment 769935 [details]
logs - disk hotplug failure
Description of problem:
Engine reports a wrong disk state after failure in disk hotplug/hotunplug
Failure in disk hotplug:
- relates to https://bugzilla.redhat.com/show_bug.cgi?id=980914
- despite disk hotplug failed, lv remain accessible. vdsm cannot deactivate it and fails.
Actual results: engine reports that disk is inactive
Expected results: engine should report that disk is active
Failure in disk hotunplug:
- relates to https://bugzilla.redhat.com/show_bug.cgi?id=981950
- engine reports that the disk is active when in fact, LV had been closed. Actual results: in this case, engine reports that disk is active
Expected results: engine should report that disk is inactive when LV attribute is -wi-a----
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. trigger a failure in disk hotplug/unplug according to reproduction steps on:
Created attachment 769945 [details]
logs - disk hotunplug failure
If hotplug fails then disk remains unplugged in engine. This has nothing to do with the LV remaining active or not.
LV remaining active might be a libvirt or qemu bug (keeping the fd open), but in any event the disk is not being accessed by qemu (i.e. it is unplugged).
Fede, wasn't the lv remaining open bug solved already?
If not, please move this bug to the correct component and rename.
*** Bug 981950 has been marked as a duplicate of this bug. ***
After a failure in disk hotunplug, lv remains open:
engine reports that the disk is active
After a failure in disk hotplug, lv remains close:
engine reports that the disk is inactive
Verified on is15:
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.