Bug 589450
Summary: | [RHEL6] Anaconda gives a traceback and does not work with encrypted pvs | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Huzaifa S. Sidhpurwala <huzaifas> | ||||
Component: | anaconda | Assignee: | Ales Kozumplik <akozumpl> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.0 | CC: | akozumpl, atodorov, jzeleny, lkocman, mganisin, mitr, msanders, notting | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | anaconda-13.21.38-1 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-07-02 20:48:33 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: | 582286 | ||||||
Attachments: |
|
Comment 2
RHEL Program Management
2010-05-06 09:36:11 UTC
Traceback (most recent call first): File "/usr/lib/anaconda/storage/devices.py", line 1699, in __init__ raise ValueError("constructor requires a list of PVs") File "/usr/lib/anaconda/storage/__init__.py", line 740, in newVG return LVMVolumeGroupDevice(name, pvs, *args, **kwargs) File "/usr/lib/anaconda/kickstart.py", line 974, in execute peSize=self.pesize/1024.0) File "/usr/lib/anaconda/kickstart.py", line 1086, in execute obj.execute(self.anaconda) File "/usr/bin/anaconda", line 1035, in <module> ksdata.execute() ValueError: constructor requires a list of PVs Bill, can you attach your kickstart please? Thanks. Ales Huzaifa, With a similar kickstart like yours I am seeing something different. Could you perhaps retest with the latest nightlies so we are sure to be on the same page? Thanks. Ales Ales, Bill just pasted the traceback from my logs, i think (In reply to comment #4) > Bill, > > can you attach your kickstart please? > > Thanks. > Ales (In reply to comment #5) > Huzaifa, > > With a similar kickstart like yours I am seeing something different. Could you > perhaps retest with the latest nightlies so we are sure to be on the same page? > > Thanks. > Ales Different as in, it works :) ? or a different traceback? Like I said on IRC, a different traceback, "new lv is too large to fit in free space". Ales, With the latest nightly i get the same traceback. this is the full traceback. patch coming soon. 13:14:23,963 CRITICAL: anaconda 13.21.33 exception report Traceback (most recent call first): File "/tmp/updates/storage/devices.py", line 1988, in _addLogVol raise DeviceError("new lv is too large to fit in free space", self.name) File "/tmp/updates/storage/devices.py", line 2175, in __init__ self.vg._addLogVol(self) File "/tmp/updates/storage/__init__.py", line 772, in newLV return LVMLogicalVolumeDevice(name, vg, *args, **kwargs) File "/tmp/updates/kickstart.py", line 513, in execute percent=self.percent) File "/tmp/updates/kickstart.py", line 1132, in execute obj.execute(self.anaconda) File "/tmp/updates/anaconda", line 1094, in <module> ksdata.execute() DeviceError: ('new lv is too large to fit in free space', 'HelpDeskRHEL6') Created attachment 412648 [details]
anaconda log from installation on encrypted lv
Hi, Huzaifas asked me to provide an update image with the fix: http://akozumpl.fedorapeople.org/bz589450.img Please let me know whether this fixes the issue so I can submit the patch. Ales Huzaifas tells me the traceback is gone and another one appears later in the install. Fixed by 03b44e6ea03fcb11aa7c69184db1d21fd279a848, will be in after anaconda-13.21.38-1. QA, Can we get a qa_ack on this one. I was overlooked before the patch was pushed. Ah yeah David, sorry about that, chasing a QA person to provide that now. Also, the traceback I am referring in Comment 14 is 590591, in fact nothing related to my fix. Ales's traceback reproduced with recent anaconda, Huzaifa's traceback reproduced with anaconda 13.21.20.4 (RHEL6.0-20100330.1). Granting qa_ack. Traceback from comment #10 reproduced with -0428.0 tree and this ks.cfg on 10GB virtio disk: bootloader --location=mbr --driveorder=vda --append="rhgb quiet" clearpart --all --initlabel part /boot --fstype=ext3 --asprimary --size=200 part pv.hd --grow --size=1 --encrypted --passphrase=firsttime volgroup HelpDeskRHEL6 --pesize=4096 pv.hd logvol /home --fstype=ext3 --name=Home --vgname=HelpDeskRHEL6 --size=500 logvol /NotBackedUp --fstype=ext3 --name=NotBackedUp --vgname=HelpDeskRHEL6 --size=1 --maxsize=8192 --grow logvol / --fstype=ext3 --name=Root --vgname=HelpDeskRHEL6 --size=4000 logvol swap --name=Swap --vgname=HelpDeskRHEL6 --size=1024 logvol /VirtualMachines --fstype=ext3 --name=VirtualMachines --vgname=HelpDeskRHEL6 --size=1000 With 0512.0 there's no traceback and install completes successfully. System is able to boot after install. Moving to VERIFIED. 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. |