Description of problem:
3.3 Incorporated the Storage Connection Manager, and patch in http://gerrit.ovirt.org/#/c/17919 works for iSCSI, but something similar will be needed in FC environments.
- SAN-replicated LUNS
- Multi-site (or DR environment).
- RHEV-M should provide a way to edit 'WWID' of LUNS part of a SD or do that automatically, enabling RHEV-M to recognize the LUNS when the replication direction is switched.
Site A is active, and site B is getting another set of LUN's replicated via SAN.
When Site A fails, SAN replication direction is switched so Site B becomes master and Site A becomes replica.
Unless you're using some way of virtualizing the storage, this will mean that LUNS will have another WWID, different to the ones in SiteA, making RHEV not able to recognize the storage thus enabling the SD's and allowing the VM's to boot.
TCMS run was executed.
Verified using RHEV3.4 av5 according to steps written in the test case:
Steps to reproduce:
-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
Doc text updated, please review for accuracy.
(In reply to Timothy from comment #8)
> Doc text updated, please review for accuracy.
A small correction: The update is performed when the storage domain is updated. Clicking edit has nothing to do with the update itself, it's just an example of when this information will become visible to the user.
Thank you, Allon. Updated.
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.
No , this solution does not work as expected.
Details forwared to TAM Paul Dwyer.
(In reply to Richard Davis from comment #12)
> No , this solution does not work as expected.
> Details forwared to TAM Paul Dwyer.
Paul, the details, please?