Bug 131353 - anaconda crashes when specifying --ondisk while using lvm
anaconda crashes when specifying --ondisk while using lvm
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-08-31 09:31 EDT by Yves Eynard
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-31 11:36:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Yves Eynard 2004-08-31 09:31:55 EDT
Description of problem:
Anaconda crashes when specifying an --ondisk when attempting to use LVM.

Version-Release number of selected component (if applicable):
RH EL AS 3.0 U2

How reproducible:
With any --ondisk= params while using lvm

Steps to Reproduce:
1. edit ks.cfg to include lvm and an --ondisk param
2. kickstart the target machine
3. look at crash dump. :-)
Actual results:

Expected results:

Additional info:
Specifying --ondisk=/dev/cciss/c0d0 when not using LVM works just
fine. If a server has more than one disk available, anaconda will
layout LVM across disks. This is undesirable.
Comment 1 Yves Eynard 2004-08-31 09:34:58 EDT
From the crash dump:

Traceback (most recent call last):
  File "/usr/bin/anaconda", line 1081, in ?
    intf.run(id, dispatch, configFileData)
  File "/usr/lib/anaconda/text.py", line 422, in run
    (step, args) = dispatch.currentStep()
  File "/usr/lib/anaconda/dispatch.py", line 262, in currentStep
  File "/usr/lib/anaconda/dispatch.py", line 157, in gotoNext
  File "/usr/lib/anaconda/dispatch.py", line 225, in moveStep
    rc = apply(func, self.bindArgs(args))
  File "/usr/lib/anaconda/autopart.py", line 1337, in doAutoPartition
    doPartitioning(diskset, partitions, doRefresh = 0)
  File "/usr/lib/anaconda/autopart.py", line 990, in doPartitioning
    (ret, msg) = processPartitioning(diskset, requests, newParts)
  File "/usr/lib/anaconda/autopart.py", line 934, in processPartitioning
    ret = fitSized(diskset, requests, 1, newParts)
  File "/usr/lib/anaconda/autopart.py", line 334, in fitSized
    disk = diskset.disks[drive]
KeyError: /dev/cciss/c0d0

and from the ks.cfg:

part /boot --fstype ext3 --size 400
part swap --size 2048

part pv.01 --size 26000 --ondisk=/dev/cciss/c0d0
volgroup vg00 pv.01
logvol / --vgname=vg00 --size=200 --name=lvol1
logvol /tmp --vgname=vg00 --size=2048 --name=lvol4
logvol /opt --vgname=vg00 --size=4096 --name=lvol5
logvol /usr --vgname=vg00 --size=4096 --name=lvol6
logvol /var --vgname=vg00 --size=1024 --name=lvol7
logvol /var/tmp --vgname=vg00 --size=4096 --name=lvol10
logvol /home --vgname=vg00 --size=200 --name=lvol11

it doesn't seem to matter where --ondisk is, or the specification,
e.g., --ondisk=/dev/cciss/c0d0, --ondisk=c0d0 --ondisk=cciss/c0d0.
Comment 2 Jeremy Katz 2004-08-31 11:36:07 EDT
You need to specify --ondisk=cciss/c0d0, not /dev/cciss/c0d0
Comment 3 Yves Eynard 2004-08-31 12:47:08 EDT

Thanks- I could have sworn that I tried that one... oh well. Sorry.
Just checked my logs and no. I didn't try it.

Anyway, when anaconda blew up, it said that "this is probably a bug"
and that I should submit it.

Thanks again

Note You need to log in before you can comment on or make changes to this bug.