Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1376022 - RFE iscsi multipath
RFE iscsi multipath
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.3.0
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Bradley Childs
Liang Xia
: NeedsTestCase, Reopened
Depends On:
Blocks: 1459922 1459925
  Show dependency treegraph
 
Reported: 2016-09-14 09:04 EDT by Marcel Wysocki
Modified: 2017-08-16 15 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1459922 1459925 (view as bug list)
Environment:
Last Closed: 2017-08-10 01:15:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 05:02:50 EDT

  None (edit)
Description Marcel Wysocki 2016-09-14 09:04:59 EDT
Description of problem:
Currently it is only possible to specify a single targetPortal.
It should be possible to specify multiple targetPortals to make use of iscsi multipath, which is the de-facto standard in environments that use iscsi.
There are workarounds to get it working but those are hacky and unclean

Ideally the PV definiton would look something like this:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: iscsi-pv
spec:
  capacity:
    storage: 1Gi
  accessModes:
    - ReadWriteOnce
  iscsi:
    - targetPortal: 10.16.154.81
      iqn: iqn.2014-12.example.server:storage.target00
      lun: 0
      fsType: 'ext4'
      readOnly: false
    - targetPortal: 10.16.154.82
      iqn: iqn.2014-12.example.server:storage.target00
      lun: 0
Comment 1 hchen 2016-09-29 10:18:02 EDT
iscsi multipath support is done in 
https://github.com/kubernetes/kubernetes/pull/21304
Comment 2 Troy Dawson 2016-10-18 12:31:50 EDT
This has been in all of the 3.3 releases.  Marking it closed.
Comment 3 Fabian Deutsch 2016-11-24 15:18:23 EST
I'm reopening this bug, because kubernetes is missing multi target support, which is essential for iSCSI multipath.

The PR mentioned in comment 1 is only adding support for /dev/mapper devices - which does not imply that kubernetes is now able to perform the necessary operations to bring up multiple paths.
Comment 5 Humble Chirammal 2017-02-16 06:05:42 EST
Multipath support is added to ISCSI plugin via https://github.com/kubernetes/kubernetes/pull/39928, it should be available from kube version 1.6
Comment 6 Liang Xia 2017-02-17 04:32:48 EST
Tested on k8s v1.6.0-alpha.2.263+9d9632ad88cf43, pod with following content can be successfully created and running with iscsi storage.

apiVersion: v1
kind: Pod
metadata:
  name: iscsipd
spec:
  containers:
  - name: iscsipd-rw
    image: aosqe/hello-openshift
    volumeMounts:
    - mountPath: "/mnt/iscsipd"
      name: iscsipd-rw
  volumes:
  - name: iscsipd-rw
    iscsi:
      targetPortal: 10.66.144.237:3260
      portals: ['10.66.147.159:3260', '10.66.144.237:3260']
      iqn: iqn.2016-04.test.com:storage.target00
      lun: 0
      fsType: ext4
      readOnly: true

Move bug to modified since the code has been merged into kubernetes, but we still need to verify it in OCP.
Comment 7 Troy Dawson 2017-04-12 09:00:31 EDT
This has been merged into ocp and is in OCP v3.6.28 or newer.
Comment 10 Fabian Deutsch 2017-05-11 14:50:14 EDT
Is any specific bug needed to get this covered in the docs as well?
Comment 19 Liang Xia 2017-07-06 01:16:28 EDT
Verified multiple targetPortals support in OCP v3.6.135 works fine.

#comment 17 is a different situation as this bug, it's another RFE, so better use another bug to track.
Comment 20 Kenjiro Nakayama 2017-07-06 01:49:09 EDT
> #comment 17 is a different situation as this bug, it's another RFE, so better use another bug to track.

Yeah, but actually this RFE has been reported with expecting below config (iqn could be specified in each targetPortal.) I think that users could expect it with this RFE.
But I know that it is too late, so we have to open another RFE.

~~~
apiVersion: v1
kind: PersistentVolume
metadata:
  name: iscsi-pv
spec:
  capacity:
    storage: 1Gi
  accessModes:
    - ReadWriteOnce
  iscsi:
    - targetPortal: 10.16.154.81
      iqn: iqn.2014-12.example.server:storage.target00
      lun: 0
      fsType: 'ext4'
      readOnly: false
    - targetPortal: 10.16.154.82
      iqn: iqn.2014-12.example.server:storage.target00
      lun: 0
~~~
Comment 23 errata-xmlrpc 2017-08-10 01:15:47 EDT
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://access.redhat.com/errata/RHEA-2017:1716

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