Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1426775 - iscsi logout even still other pods use iscsi on same node
iscsi logout even still other pods use iscsi on same node
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage (Show other bugs)
3.3.1
x86_64 Linux
unspecified Severity high
: ---
: 3.3.1
Assigned To: Bradley Childs
Jianwei Hou
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-02-24 15:03 EST by Troy Dawson
Modified: 2017-03-15 16:03 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: issue if same iscsi device used by multiple pods on same node. Consequence: When one pod would shut down, the iscsi device for the other pod would be unavailable. Fix: code change. Result: Resolved.
Story Points: ---
Clone Of: 1419607
Environment:
Last Closed: 2017-03-15 16:03:16 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
Origin (Github) 12990 None None None 2017-02-24 15:03 EST
Red Hat Product Errata RHBA-2017:0512 normal SHIPPED_LIVE OpenShift Container Platform 3.4.1.10, 3.3.1.17, and 3.2.1.28 bug fix update 2017-03-15 20:01:17 EDT

  None (edit)
Comment 1 Troy Dawson 2017-02-24 15:27:12 EST
This has been merged into ocp and is in OCP v3.4.1.8 or newer.
Comment 3 Jianwei Hou 2017-02-27 01:05:46 EST
Verified on 
openshift v3.3.1.15
kubernetes v1.3.0+52492b4
etcd 2.3.0+git

Steps:1
1. Create two Pods on same nodes and mounts same iscsi volume over same session. Make sure their only difference is the LUN number.
2. Verify Pods  are both running.
3. Delete one of the Pods.
4. The remaining Pod is still running.
Comment 5 errata-xmlrpc 2017-03-15 16:03:16 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/RHBA-2017:0512

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