Bug 772977
| Summary: | Anaconda tries to use read-only DASD drive for installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Stodola <jstodola> |
| Component: | anaconda | Assignee: | David Cantrell <dcantrell> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | dcantrell, jreed |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | s390x | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | anaconda-13.21.177-1 | Doc Type: | Bug Fix |
| Doc Text: |
No documentation needed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 09:58:32 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: | |||
| Bug Blocks: | 760559, 840685 | ||
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. *** Bug 820022 has been marked as a duplicate of this bug. *** This has been fixed upstream and a patch is available for RHEL6. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. Verified using compose RHEL6.4-20121206.0 with anaconda-13.21.187-1.el6. Installation finished successfully, anaconda didn't allow to use read-only DASD drive for installation. 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. http://rhn.redhat.com/errata/RHBA-2013-0373.html |
Description of problem: When installation is stared with something like: DASD='3527,3627(ro)' in CMS config file, anaconda allows to use both 3527 and 3627 for partitioning. This results in a traceback when writing changes to disks: anaconda 13.21.149 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/lvm.py", line 188, in pvcreate raise LVMError("pvcreate failed for %s: %s" % (device, msg)) File "/usr/lib/anaconda/storage/formats/lvmpv.py", line 117, in create lvm.pvcreate(self.device, progress=w) File "/usr/lib/anaconda/storage/deviceaction.py", line 290, in execute options=self.device.formatArgs) File "/usr/lib/anaconda/storage/devicetree.py", line 713, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 344, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 110, in turnOnFilesystems anaconda.id.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1390, in nextClicked self.anaconda.dispatch.gotoNext() LVMError: pvcreate failed for /dev/dasdc1: 10:03:17,549 ERROR : Can't open /dev/dasdc1 exclusively. Mounted filesystem? Version-Release number of selected component (if applicable): RHEL-6.2 anaconda-13.21.149-1.el6 How reproducible: always Steps to Reproduce: 1. modify CMS config file, add '(ro)' to any DASD device 2. start the installation 3. select all available DASD devices 4. let anaconda to create auto-partitionig Actual results: Traceback when writing partitioning to disks Expected results: User should not be allowed to partition read-only DASD drives during the installation