Bug 1451852 – Unable to boot from iSCSI SAN boot volume after enabling multipath in initramfs

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

Bug 1451852 - Unable to boot from iSCSI SAN boot volume after enabling multipath in initramfs

Summary:	Unable to boot from iSCSI SAN boot volume after enabling multipath in initramfs

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	device-mapper-multipath (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Ben Marzinski
QA Contact:	Lin Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1445958
Blocks:
	Show dependency tree / graph

Reported:	2017-05-17 12:13 EDT by Ben Marzinski
Modified:	2018-04-10 12:10 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:	device-mapper-multipath-0.4.9-115.el7
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:	1445958
Environment:
Last Closed:	2018-04-10 12:10:28 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
Red Hat Product Errata	RHEA-2018:0884	normal	SHIPPED_LIVE	device-mapper-multipath bug fix and enhancement update	2018-04-10 09:47:14 EDT

Groups: None (edit)

Comment 1 Lin Li 2017-07-12 05:21:56 EDT

Hello shivamerla1,
Because we don't have Nimble storage, could you provide test result once the fixed package is available?
Thanks.

Comment 2 Ben Marzinski 2017-10-11 14:11:57 EDT

changed fast_io_fail_tmo to 5

Comment 6 Lin Li 2018-01-29 13:04:46 EST

change to verified according to comment 4.

Comment 9 errata-xmlrpc 2018-04-10 12:10:28 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/RHEA-2018:0884

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