Description of problem: Customer multipath -l output is like: 3600d0230000000000e13955cc3757800 dm-1 WINSYS,SF2372 size=269G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 6:0:0:0 sdb 8:16 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 7:0:0:0 sdf 8:80 active ready running Looking at install.py from ovirtnode (http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=blob;f=src/ovirtnode/install.py;h=cf8ff33f17b0cf202329d0e346e75ee395b83bf5;hb=HEAD), line 522/523: grub_disk_cmd = "multipath -l \"" + self.disk + \ "\" | awk '/ active / {print $3}' | head -n1" The right column for sdb device would be the 4th and it's looking for the 3rd ({print $3}) instead. For device sdf or single group of devices the parsing is right. Version-Release number of selected component (if applicable): rhev-h from RHEV 3.2 How reproducible: always Actual results: Unable to install RHEV-H Additional info: HP Hardware
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Seems Fabian's patch fixed this issue： http://gerrit.ovirt.org/#/c/20558/
virt-qa has no specififc multipath device that could multipath -l output info like this: | `- 6:0:0:0 sdb 8:16 active ready running so need the reporter to verify this bug after the patch is merged into offical build.
I can confirm a RHEV-H build with the patch included fixes the problem. Thanks!
This bug is currently attached to errata RHBA-2013:15277. 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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thank you for your help.
Re-testing on QE env. again according to comment 20. Thanks.