Bug 1309348

Summary:	DASD disk is not always brought online by linuxrc
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Stodola <jstodola>
Component:	anaconda	Assignee:	Samantha N. Bueno <sbueno>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.8	CC:	hannsj_uhl, sbueno
Target Milestone:	rc
Target Release:	---
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-13.21.248-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-10 20:47:13 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:	1286535

Description Jan Stodola 2016-02-17 14:43:57 UTC

Description of problem:
In some cases, a DASD disk is not brought online by linuxrc. The following conditions help to reproduce this issue:

* 2 CPUs (unable to reproduce with 1 CPU)
* one FBA DASD disk (unable to reproduce with ECKD DASD)
* configuration in CMS config file
* tested in a z/VM guest

Version-Release number of selected component (if applicable):
RHEL-6.7 GA
RHEL-6.8 Alpha (anaconda-13.21.246-1.el6)

How reproducible:
always when the conditions above are met

Steps to Reproduce:
1. see description

Actual results:
DASD is not brought online by linuxrc

Expected results:
DASD is brought online by linuxrc

Comment 1 Jan Stodola 2016-02-17 14:55:11 UTC

The following pull request fixes this issue for me:
https://github.com/rhinstaller/anaconda/pull/511

Comment 2 Samantha N. Bueno 2016-02-17 19:44:19 UTC

Simple enough to fix and low risk. Thanks for the patch.

Comment 4 Jan Stodola 2016-03-10 14:05:02 UTC

No longer reproducible with anaconda-13.21.249-1.el6.
Moving to VERIFIED.

Comment 6 errata-xmlrpc 2016-05-10 20:47:13 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://rhn.redhat.com/errata/RHBA-2016-0798.html