RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 772977 - Anaconda tries to use read-only DASD drive for installation
Summary: Anaconda tries to use read-only DASD drive for installation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.2
Hardware: s390x
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact: Release Test Team
URL:
Whiteboard:
: 820022 (view as bug list)
Depends On:
Blocks: 760559 840685
TreeView+ depends on / blocked
 
Reported: 2012-01-10 15:23 UTC by Jan Stodola
Modified: 2013-02-21 09:58 UTC (History)
2 users (show)

Fixed In Version: anaconda-13.21.177-1
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:58:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0373 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2013-02-20 20:52:28 UTC

Description Jan Stodola 2012-01-10 15:23:28 UTC 
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
Comment 3 RHEL Program Management 2012-05-03 05:01:06 UTC 
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.
Comment 4 David Cantrell 2012-05-11 19:43:52 UTC 
*** Bug 820022 has been marked as a duplicate of this bug. ***
Comment 6 Jesse Keating 2012-06-28 20:07:07 UTC 
This has been fixed upstream and a patch is available for RHEL6.
Comment 7 RHEL Program Management 2012-07-16 22:46:12 UTC 
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.
Comment 9 Jan Stodola 2012-12-11 12:04:25 UTC 
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.
Comment 11 errata-xmlrpc 2013-02-21 09:58:32 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.

http://rhn.redhat.com/errata/RHBA-2013-0373.html
Note You need to log in before you can comment on or make changes to this bug.