Bug 1097324

Summary:	CMS Configuration File option DASD=none invalid
Product:	Red Hat Enterprise Linux 7	Reporter:	Petr Bokoc <pbokoc>
Component:	doc-Installation_Guide	Assignee:	Tomas Capek <tcapek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dracut-maint-list, hyrum.smith, jjarvis, jstodola
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1096979	Environment:
Last Closed:	2014-06-11 13:09:59 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:	1096979
Bug Blocks:

Comment 1 Jan Stodola 2014-05-13 15:55:16 UTC

DASD=none is mentioned twice in the document:

1) 18.3. Installation Network Parameters:

-----------
For FCP-only environments, specify DASD='none'. 
----------

2) 15.16.1.2.2. FCP Devices:

---------
Important
The installation program requires the definition of a DASD. For a SCSI-only installation, enter none as the parameter interactively during phase 1 of an interactive installation, or add DASD=none in the parameter or CMS configuration file. This satisfies the requirement for a defined DASD parameter, while resulting in a SCSI-only environment.
---------

Since it is not required to define any DASD and there is no interactive phase 1, this section could be removed from the document.

Comment 3 Jan Stodola 2014-05-21 10:35:58 UTC

Thanks Tomas, the changes look good to me.