Bug 1623650

Summary:	iscsi initiator can not boot after reboot
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Yevhenii Shapovalov <yshapova>
Component:	iSCSI	Assignee:	Mike Christie <mchristi>
Status:	CLOSED ERRATA	QA Contact:	Manohar Murthy <mmurthy>
Severity:	high	Docs Contact:	Bara Ancincova <bancinco>
Priority:	high
Version:	3.1	CC:	agunn, ceph-eng-bugs, ceph-qe-bugs, hnallurv, jdillama, mchristi, tchandra
Target Milestone:	z1	Keywords:	Reopened
Target Release:	3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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 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-11-09 00:59:32 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:	1584264

Description Yevhenii Shapovalov 2018-08-29 19:47:15 UTC

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 05:31:15 UTC


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

Comment 24 errata-xmlrpc 2018-11-09 00:59:32 UTC

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-2018:3530