Bug 1376022
| Summary: | RFE iscsi multipath | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Marcel Wysocki <mwysocki> | |
| Component: | RFE | Assignee: | Bradley Childs <bchilds> | |
| Status: | CLOSED ERRATA | QA Contact: | Liang Xia <lxia> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 3.3.0 | CC: | aos-bugs, bchilds, bleanhar, fdeutsch, hchen, hchiramm, jokerman, knakayam, lxia, mmccomas, prasanna.kalever, rfoyle, tdawson, tibrahim | |
| Target Milestone: | --- | Keywords: | NeedsTestCase, Reopened | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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 05:15:47 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1459922, 1459925 | |||
iscsi multipath support is done in https://github.com/kubernetes/kubernetes/pull/21304 This has been in all of the 3.3 releases. Marking it closed. 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. Multipath support is added to ISCSI plugin via https://github.com/kubernetes/kubernetes/pull/39928, it should be available from kube version 1.6 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.
This has been merged into ocp and is in OCP v3.6.28 or newer. Is any specific bug needed to get this covered in the docs as well? 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 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
~~~
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 |
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