Bug 1623650 – iscsi initiator can not boot after reboot

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1623650 - iscsi initiator can not boot after reboot

Summary:	iscsi initiator can not boot after reboot

Status:	VERIFIED

Aliases:	None

Product:	Red Hat Ceph Storage
Classification:	Red Hat
Component:	iSCSI (Show other bugs)
Sub Component:
Version:	3.1
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	z1
Target Release:	3.1
Assigned To:	Mike Christie
QA Contact:	Manohar Murthy
Docs Contact:	Bara Ancincova

URL:
Whiteboard:
Keywords:	Reopened

Depends On:
Blocks:	1584264
	Show dependency tree / graph

Reported:	2018-08-29 15:47 EDT by Yevhenii Shapovalov
Modified:	2018-10-24 06:32 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	tcmu-runner-1.4.0-0.4.el7cp
Doc Type:	Bug Fix
Doc Text:	.Discovering iSCSI paths during the boot, setup, or scanning process no longer causes the DM-Multipath feature to fail to set up _[fixed by 3.1z1]_ During device and path setup, the initiator sent commands to all paths at the same time. This behavior caused the Ceph iSCSI gateways to take the RBD lock from one device and set it on another device. In some cases, the iSCSI gateway interpreted the lock being taken away in this manner as a hard error and escalated its error handler by dropping the iSCSI connection, reopening the RBD devices to clear old states, and then enabling the iSCSI target port group to allow a new iSCSI connection. This caused a disruption to the device and path discovery when disabling and enabling the iSCSI target port group. In turn, the multipath I/O layer continually was disabling and enabling all paths and I/O was suspended, or device and path discovery could fail and the device was not setup. This bug has been fixed, and rebooting an iSCSI initiator with connected devices no longer leads to this error.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-05 16:31:05 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
Github	open-iscsi/tcmu-runner/commit/8c26e8f01235da8b08505c647c7c8104af947e9c	None	None	None	2018-09-22 15:36 EDT
Github	open-iscsi/tcmu-runner/commit/cd921611dd23fec5573512432c3c796e7f2cca02	None	None	None	2018-09-22 15:35 EDT
Github	open-iscsi/tcmu-runner/pull/477	None	None	None	2018-09-12 11:39 EDT

Groups: None (edit)

Description Yevhenii Shapovalov 2018-08-29 15:47:15 EDT

Description of problem:
Rebooting of iscsi initiator with connected iscsi devices leads to error during node boot.

Version-Release number of selected component (if applicable):
Rhel 7.5 Ceph 3.0 and 3.1

How reproducible:
100%

Steps to Reproduce:
1. Deploy ceph cluster
2. Setup iscsi target
3. Setup iscsi initiator
4. Connect initiator to target
5. Reboot initiator

Actual results:
Initiator node can not boot

Expected results:
Initiator node successfully booted

Additional info:

Comment 9 Mike Christie 2018-09-05 01:31:15 EDT


*** This bug has been marked as a duplicate of bug 1623601 ***

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