Bug 1393372 - iscsi: request and parse ipv6 targets from vdsm (in clusterLevel>=4.1) - engine side
Summary: iscsi: request and parse ipv6 targets from vdsm (in clusterLevel>=4.1) - engi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.6
: 4.2.6
Assignee: shani
QA Contact: Shir Fishbain
URL:
Whiteboard:
Depends On: 1612958
Blocks: RHEV_IPv6
TreeView+ depends on / blocked
 
Reported: 2016-11-09 12:21 UTC by Dan Kenigsberg
Modified: 2018-09-03 15:10 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Discover and login to ipv6 addresses while creating a new iSCSI storage domain. Reason: In case of trying to discover an ipv6 address, there's an error message. Therefore only discovery for ipv4 is being supported today. Result: The user can successfully discover ipv6 addresses. This is enabled by default on clusterLevel >=4.3, but may be enabled manually on clusterLevel=4.2 if all of your hosts are >= 4.2.6 with engine-config -s ipv6IscsiSupported=true --cver=4.2
Clone Of: 1308306
Environment:
Last Closed: 2018-09-03 15:10:43 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2?
danken: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 93694 0 master MERGED core: Support IPv6 targets discovery 2018-08-21 10:02:43 UTC
oVirt gerrit 93695 0 master MERGED webadmin: Visually support ipv6 address 2018-08-21 10:02:45 UTC
oVirt gerrit 93825 0 ovirt-engine-4.2 MERGED core: Support IPv6 targets discovery 2018-08-21 11:53:31 UTC
oVirt gerrit 93826 0 ovirt-engine-4.2 MERGED webadmin: Visually support ipv6 address 2018-08-21 11:53:35 UTC
oVirt gerrit 93959 0 master MERGED core: Add ipv6IscsiSupported to engine-config 2018-08-28 10:31:42 UTC
oVirt gerrit 93974 0 ovirt-engine-4.2 MERGED core: Add ipv6IscsiSupported to engine-config 2018-08-29 08:20:00 UTC

Description Dan Kenigsberg 2016-11-09 12:21:42 UTC
Now that Vdsm accepts ipv6_enabled in ISCSIConnection.discoverSendTargets, Engine should set it to True and parse the ipv6 output.


+++ This bug was initially created as a clone of Bug #1308306 +++

Comment 1 Yaniv Kaul 2017-06-06 20:49:11 UTC
All gerrit links above are merged. What else is needed here?

Comment 2 Dan Kenigsberg 2017-06-06 22:00:36 UTC
All the patches here are vdsm's, and they are here only because it is a clone of the vdsm bug.

Engine work has not started.

Comment 5 Dan Kenigsberg 2018-07-29 19:22:43 UTC
Would you agree to look at this sooner than later?

Comment 6 Red Hat Bugzilla Rules Engine 2018-07-29 19:22:49 UTC
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 7 Tal Nisan 2018-08-02 14:30:51 UTC
(In reply to Dan Kenigsberg from comment #5)
> Would you agree to look at this sooner than later?

You didn't leave me much choice, you already targeted it on my behalf :)

Comment 8 Nir Soffer 2018-08-07 11:26:21 UTC
(In reply to Dan Kenigsberg from comment #0)
> Now that Vdsm accepts ipv6_enabled in ISCSIConnection.discoverSendTargets,

Dan, has this flag, but it seems that the author adding this flag never tested
it, see bug 1612958 :-)

Comment 9 Sandro Bonazzola 2018-08-28 10:08:24 UTC
Moved to 4.2.7 not being marked as blocker for 4.2.6.

Comment 10 Shir Fishbain 2018-08-30 09:14:41 UTC
ipv6IscsiSupported is true for 4.2 and still, discovery with ipv6 doesn't expose targets.

The message that appears :
"No new devices were found. This may be due to either: incorrect multipath configuration on the Host or wrong address of the iscsi target or a failure to authenticate on the target device. Please consult your Storage Administrator"
                                            
I changed the value in vdc_options and restart ovirt-engine service.
 
engine=# select * from vdc_options where option_name = 'ipv6IscsiSupported';
 option_id |    option_name     | option_value | version 
-----------+--------------------+--------------+---------
       658 | ipv6IscsiSupported | false        | 3.6
       659 | ipv6IscsiSupported | false        | 4.0
       660 | ipv6IscsiSupported | false        | 4.1
       661 | ipv6IscsiSupported | true         | 4.2
(4 rows)

4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7

Comment 11 shani 2018-08-30 09:53:43 UTC
Hi,
From a brief view on your engine log, it seems that you have a connection problem while trying to access the ipv6 address:

[root@storage-ge16-vdsm2 ~]#  ping6 2620:52:0:2300:868f:69ff:fef9:6760
connect: Network is unreachable

Therefore, the discovery won't work unless the connection will be set up correctly.

Comment 12 Shir Fishbain 2018-09-03 13:17:24 UTC
Discovery with ipv6 expose targets

2018-09-03 15:28:59,653+03 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (default task-35) [bb66342e-bacf-4372-9162-5d8033478c3e] START, ConnectStorageServerVDSCommand(HostName
= host_mixed_1, StorageServerConnectionManagementVDSParameters:{hostId='f3d688d1-2888-48f3-a09b-ec7ed8363c22', storagePoolId='00000000-0000-0000-0000-000000000000', storageType='ISCSI', connectionList='[Storage
ServerConnections:{id='null', connection='2620:52:0:2300:868f:69ff:fef9:6760', iqn='iqn.2018-01.com.shani-ipv6.1:444', vfsType='null', mountOptions='null', nfsVersion='null', nfsRetrans='null', nfsTimeo='null', 
iface='null', netIfaceName='null'}]', sendNetworkEventOnFailure='true'}), log id: 341c90fa

ovirt-engine-4.2.6.4-0.1.el7ev.noarch
vdsm-4.20.39-1.el7ev.x86_64


Note You need to log in before you can comment on or make changes to this bug.