Red Hat Bugzilla – Bug 586410
list-harddrives command broken in kickstart/anaconda environment for %pre/%post
Last modified: 2010-07-02 16:47:36 EDT
Created attachment 409480 [details]
list-harddrives crash output
Description of problem:
The "list-harddrives" utility crashes on CDROM drive discovery with DiskLabelException "unrecognized disk label".
This is a popular command to use in kickstart %pre and %post scripts to provide an easy to use method of getting information about all of the disks connected to the system.
Version-Release number of selected component (if applicable):
RHEL 6 Beta 1
Run list-harddrives command inside command shell or in %pre/%post scripts during kickstart/anaconda environment.
Steps to Reproduce:
1. run list-harddrives command
2. command crashes on cdrom
A properly formatted list of hard drives on system and their sizes.
Attached are screenshots(was using VMWare Console so have no copy/paste) of the output from list-harddrives crash, as well as the example output from running parted against the device as well which is apparently what output is being parsed by the list-harddrives python code that causes the problem.
Created attachment 409481 [details]
parted example output on same devices
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Hello, VERIFIED on build RHEL6.0-20100512.0 with anaconda-13.21.39-1.el6. No traceback displayed, only /dev/sda has been checked.
Closing as verified.
*** Bug 600469 has been marked as a duplicate of this bug. ***
Hi, This bug also exists in Fedora 13 anaconda-13.42-1.fc13.i686 as was reported in Bug 600469. I notice this is Fixed in Version: anaconda-13.21.33-1 has the fix been forward ported?
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.