+++ This bug was initially created as a clone of Bug #1036731 +++ What is the nature and description of the request? Hosted engine needs to be able to be deployed for iSCSI data centers Why does the customer need this? (List the business requirements here) We see a lot more customers running iSCSI data centers than NFS, and hosted engine was one of the major pushes for upgrading to 3.3. Is there already an existing RFE upstream or in Red Hat Bugzilla? Yes, 1036731 from which this bug is cloned. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? N/A at this time
please note while hosted engine still doesn't work on an iscsi storage domain, you can run it on hosts in an iscsi data center. i.e., only the storage domain for the hosted engine needs to be NFS for now, and you can mix that specific storage domain with in an iscsi DC.
In 3.4 we started using shared DC instead of ISCSI/NFS/etc' So it sounds like we need to test shared DC where the HE disk is using ISCSI below that am I right?
(In reply to Aharon Canan from comment #5) > In 3.4 we started using shared DC instead of ISCSI/NFS/etc' > > So it sounds like we need to test shared DC where the HE disk is using ISCSI > below that > > am I right? From the Bug #1036731 I understand that during hosted-engine --deploy, customer required to get boot from SAN (iscsi&FC) in addition to already existing NFS (currently the one and only) option. This means , that SD of HE (which is hidden via UI) could be connected to iscsi/FC.
(In reply to Aharon Canan from comment #5) > In 3.4 we started using shared DC instead of ISCSI/NFS/etc' > > So it sounds like we need to test shared DC where the HE disk is using ISCSI > below that > > am I right? I don't understand what you mean. This feature is adding the support for deploying the HE directly to the iscsi.
Removing bug #1036731 from dependencies, FC support shouldn't block iSCSI support
Returning to ASSIGNED due to BZ #1150427
All relevant BZs are ON QA.
Verified on ovirt-hosted-engine-setup-1.2.1-4.el6ev.noarch Host and RHEVM runs on rhel6.6 engine - rhevm-3.5.0-0.21.el6ev.noarch
Moving from verified to on-qa because we tested the installation part - see comment 13 Storage team still needs to check their part and verified...
TCMS run was executed: https://tcms.engineering.redhat.com/run/191449/ All the critical issues have been fixed, moving to VERIFIED.
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. https://rhn.redhat.com/errata/RHSA-2015-0158.html