Bug 131353 - anaconda crashes when specifying --ondisk while using lvm
Summary: anaconda crashes when specifying --ondisk while using lvm
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-31 13:31 UTC by Yves Eynard
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-31 15:36:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yves Eynard 2004-08-31 13:31:55 UTC
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 13:34:58 UTC
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
    self.gotoNext()
  File "/usr/lib/anaconda/dispatch.py", line 157, in gotoNext
    self.moveStep()
  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 15:36:07 UTC
You need to specify --ondisk=cciss/c0d0, not /dev/cciss/c0d0

Comment 3 Yves Eynard 2004-08-31 16:47:08 UTC
Jeremy,

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
Yves


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