Bug 1536055

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

I've tried to deploy Node 0 over iSCSI with 3 different interfaces configured on storage side (10.35.163.32 , 10.35.163.42, 10.35.163.43) under the same portal, but discovery on host, did not found additional two (10.35.163.42, 10.35.163.43), it shown only one from three available:
[ INFO  ] changed: [localhost]
          Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: iscsi
          Please specify the iSCSI portal IP address: 10.35.163.32
          Please specify the iSCSI portal port [3260]: 
          Please specify the iSCSI discover user: 
          Please specify the iSCSI discover password: 
          Please specify the iSCSI portal login user: 
          Please specify the iSCSI portal login password: 
[ INFO  ] Discovering iSCSI targets
[ INFO  ] TASK [Gathering Facts]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [include_tasks]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [Obtain SSO token using username/password credentials]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [Prepare iSCSI parameters]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [Fetch host facts]
[ INFO  ] ok: [localhost]
[ INFO  ] TASK [iSCSI discover with REST API]
[ INFO  ] ok: [localhost]
          The following targets have been found:
                [1]     iqn.2005-10.org.freenas.ctl:iscsi_shetarget
                        TPGT: -1, portals:
                                10.35.163.32:3260
         
          Please select a target (1) [1]:  

"multipath -ll" on host, shown nothing.


Tested on these components:
rhvm-appliance-4.2-20180202.0.el7.noarch
ovirt-hosted-engine-ha-2.2.5-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.10-1.el7ev.noarch
Linux 3.10.0-693.19.1.el7.x86_64 #1 SMP Thu Feb 1 12:34:44 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Logs from host attached.

Created attachment 1397854 [details]
alma03 logs

I think that the SAN side was simply not configured for multipath

Thanks to Simone, now it looks fine:
[ INFO  ] ok: [localhost]
          The following targets have been found:
                [1]     iqn.2005-10.org.freenas.ctl:iscsi-shetarget
                        TPGT: 2, portals:
                                10.35.163.32:3260
                                10.35.163.42:3260
                                10.35.163.43:3260

         [ INFO  ] ok: [localhost]
          The following luns have been found on the requested target:
                [1]     36589cfc0000006465c444562a2816b2f       123GiB  FreeNAS iSCSI Disk
                        status: free, paths: 3 active
         
          Please select the destination LUN (1) [1]: 
alma03 ~]# multipath -ll
36589cfc0000006465c444562a2816b2f dm-0 FreeNAS ,iSCSI Disk      
size=123G features='0' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=1 status=active
| `- 7:0:0:0 sdc 8:32 active ready running
|-+- policy='service-time 0' prio=1 status=enabled
| `- 6:0:0:0 sdb 8:16 active ready running
`-+- policy='service-time 0' prio=1 status=enabled
  `- 8:0:0:0 sdd 8:48 active ready running

Moving to verified due to previous comment.

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.