Hide Forgot
Description of problem: When expanding a iscsi storage domain it the following error happens: 2013-09-27 14:30:52,362 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.ExtendStorageDomainVDSCommand] (ajp-/127.0.0.1:8702-4) Error code InvalidPhysDev and error message IRSGenericException: IRSErrorException: Failed to ExtendStorageDomainVDS, error = Invalid physical device: ('360a9800064775066476f7470697a3959',) Version-Release number of selected component (if applicable): 4.12.0 How reproducible: Try to expand an iscsi storage domain Steps to Reproduce: 1.Setup a cluset with iscsi domain and 1 host 2.Expand the domain with a new device 3. Actual results: Expansion failed and error is shown Expected results: Expansion happend Additional info: Putting some debug prints on vdsm/storage/blockSD.py near the line 706 shows that the device name and the expected name do not match properly (full path vs just device name): Code snippet: for dev in devlist: if dev in knowndevs: devices.append(dev) else: raise se.InvalidPhysDev(dev) Log message: Thread-67::ERROR::2013-09-27 14:18:04,636::blockSD::706::Storage.StorageDomain::(extend)known: ['/dev/mapper/1kjachim02', '/dev/mapper/1kjachim01', '/dev/mapper/1kjachim03'], dev: 1kjachim03
David, is it a regression? is it reproducible?
looks like a regression introduced by: http://gerrit.ovirt.org/#/c/17967/1
verified using is17 passed manually and automation as well
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: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 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. http://rhn.redhat.com/errata/RHBA-2014-0040.html