Bug 1096979
Summary: | CMS Configuration File option DASD=none invalid | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Hyrum <hyrum.smith> | |
Component: | dracut | Assignee: | dracut-maint | |
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | |
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.0 | CC: | dhorak, dracut-maint-list, harald, jjarvis, jstodola | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | s390x | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Known Issue | ||
Doc Text: |
The "DASD=" option in the CMS configuration file defines the Direct Access Storage Device (DASD) or range of DASDs to configure during the installation. To indicate that no DASD is present, remove the option from the configuration file because specifying "DASD=none" is not valid.
With this update specifying "DASD=none" is possible again.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1097324 1097328 (view as bug list) | Environment: | ||
Last Closed: | 2015-03-05 08:20:55 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: | 1097324 |
Description
Hyrum
2014-05-12 20:57:18 UTC
There is an easy workaround: Instead of using DASD="none", don't use the DASD= parameter at all. Where should this be documented, Installation Guide or Technical Notes? We should get this cloned as documentation tracker against the targeted 7.0 documentation. It could be documented in both documentations, I will clone the bug. Retested with dracut-033-227.el7. Dracut ignores DASD="none" in CMS config file and no error message is printed. Moving to VERIFIED. 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-2015-0375.html |