Bug 1426778 – iscsi logout even still other pods use iscsi on same node

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1426778 - iscsi logout even still other pods use iscsi on same node

Summary:	iscsi logout even still other pods use iscsi on same node

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage (Show other bugs)
Sub Component:
Version:	3.5.0
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Bradley Childs
QA Contact:	Jianwei Hou
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-02-24 15:07 EST by Troy Dawson
Modified:	2017-07-24 10 EDT (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: Error when multiple iscsi luns on same node Consequence: iscsi device logout even if other iscsi devices in use on same node.
Story Points:	---
Clone Of:	1419607
Environment:
Last Closed:	2017-04-12 15:13:50 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Origin (Github)	12990	None	None	None	2017-02-24 15:07 EST
Red Hat Product Errata	RHBA-2017:0884	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.5 RPM Release Advisory	2017-04-12 18:50:07 EDT

Groups: None (edit)

Comment 1 Troy Dawson 2017-02-24 15:27:39 EST

This has been merged into ocp and is in OCP v3.5.0.34 or newer.

Comment 3 Jianwei Hou 2017-02-27 05:36:25 EST

Verified on
openshift v3.5.0.34
kubernetes v1.5.2+43a9be4
etcd 3.1.0

Steps:
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-04-12 15:13:50 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:0884

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