LUN change is detected by engine. TCMS run was executed: https://tcms.engineering.redhat.com/run/124090/ Verified according to the following steps: -Install RHEL on host (make sure the host is not exposed to any devices via FC) -Once host has RHEL OS installed, Expose a 20G LUN to it from the storage server via FC -Create a FC storage domain resides on a 20G physical volume -Activate the domain -Issue SAN copy from storage server side - copy the data from the 20G LUN to a new 25G LUN -Connect the new LUN (25G) to the host (LUN masking) and remove the original LUN (20G) -Reboot the host so the FC connected devices will be rescanned -Activate the storage domain -Under 'Storage domains' tab, pick the relevant domain and click on 'Edit'. LUN ID changed to the new one ==== Verified using RHEV3.3.2 - IS35
This bug is currently attached to errata RHBA-2014:17286. 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-0384.html