Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1497059

Summary:	Core was generated by `mpathpersist -o -G -S 1AA00C5202 /dev/mapper/mpathf' [rhel-6.9.z]
Product:	Red Hat Enterprise Linux 6	Reporter:	Oneata Mircea Teodor <toneata>
Component:	device-mapper-multipath	Assignee:	Ben Marzinski <bmarzins>
Status:	CLOSED ERRATA	QA Contact:	Lin Li <lilin>
Severity:	low	Docs Contact:
Priority:	high
Version:	6.8	CC:	agaikwad, agk, bmarzins, heinzm, jbrassow, jmagrini, jreznik, lilin, msnitzer, mthacker, nkshirsa, prajnoha, rbalakri, zkabelac
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	device-mapper-multipath-0.4.9-100.el6_9.1	Doc Type:	Bug Fix
Doc Text:	Prior to this update, the mpathpersist utility sometimes attempted to wait on threads that it did not create. As a consequence, mpathpersist terminated unexpectedly if there was a registration conflict on one of the paths. With this update, mpathpersist now waits only for threads that it creates. As a result, mpathpersist no longer crashes in this situation.	Story Points:	---
Clone Of:	1447328	Environment:
Last Closed:	2017-11-14 20:53:03 UTC	Type:	---
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:	1447328, 1497083
Bug Blocks:

Description Oneata Mircea Teodor 2017-09-29 06:45:43 UTC

This bug has been copied from bug #1447328 and has been proposed to be backported to 6.9 z-stream (EUS).

Comment 2 Ben Marzinski 2017-10-02 21:41:15 UTC

Fix backported.

Comment 4 Ben Marzinski 2017-10-02 22:55:02 UTC

The easiest way to reproduce this should be to create a multipath device with multiple paths, and reservation_key set.  Then, use sg_persist to create a registration with a different key from reservation_key on one of the paths devices directly.  This must not not be the first path of the multipath device. Then use mpathpersist to try to create a registration with the reservation_key from the config file.  This will cause a conflict on the path that already has a reservation, and force multipath to try to back out the existing reservation, which should trigger this bug.

Comment 9 errata-xmlrpc 2017-11-14 20:53:03 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-2017:3199