Bug 435998
| Summary: | anaconda traceback in migrateFilesystems after filesystems are formatted but before packages are installed | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Mike Gahagan <mgahagan> |
| Component: | anaconda | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.2 | CC: | atodorov, emcnabb, jlaska, pjones |
| Target Milestone: | beta | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2008-0397 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-21 15:33:25 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: | |||
| Attachments: | |||
|
Description
Mike Gahagan
2008-03-04 20:16:35 UTC
Created attachment 296791 [details]
screenshot of traceback 1/3
Created attachment 296792 [details]
anaconda traceback screenshot 2/3
Created attachment 296793 [details]
Anaconda traceback 3/3
Created attachment 296797 [details]
log of traceback from i386 baremetal system
traceback from logfile attachment in comment 4 Traceback (most recent call first): File "/usr/lib/anaconda/fsset.py", line 1834, in migrateFilesystems entry.options = entry.options.replace(",_netdev",",_rnetdev") File "/usr/lib/anaconda/packages.py", line 127, in doMigrateFilesystems anaconda.id.fsset.migrateFilesystems (anaconda.rootPath) File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1018, in nextClicked self.anaconda.dispatch.gotoNext() File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1045, in handleRenderCallback self.currentWindow.renderCallback() AttributeError: 'NoneType' object has no attribute 'replace' Local variables in innermost frame: entry: fsentry -- device: VolGroup00/LogVol00 mountpoint: / fsystem: ext3 format: True ismounted: 1 options: 'defaults' bytesPerInode: 4096 label: None self: <fsset.FileSystemSet instance at 0xb7bebf0c> chroot: /mnt/sysimage mountpoint: / _rnetdev ... hrmm. Adding pjones to the cc list for some thoughts. wiping the partition table on the drive, then initilizing the drive in anaconda apperantly gets around this bug.. I'll try doing a second install to the same partitions/LV's once this install completes. Created attachment 296804 [details]
updates.img to test with
Please try to replicate with the attached update image.
Created attachment 296806 [details]
updates.img to test with
(Sorry about that last one, it may have been misconstructed.)
Created attachment 296807 [details]
the patch applied to create the updates.img
updated reproducer instructions: 1. Install the 0303.0 tree to a blank (unpartitioned drive) 2. Run install of 0303.0 tree again, create custom partition layout, choose pre-existing partitoins/LV's from last install, format and make the same mountpoints as before 3. choose some packages to install (I only chose "software development") 4. click ok to start the install, watch traceback appear after disk(s) are formatted, but just before package installation would start. Created attachment 296813 [details] log files from second traceback in comment 11 - includes partition/lvm information I started an install with the updates.img in comment 9 .. so far so good.. it is installing packages now... I'll provide another update once it is done. Install using the updates.img file was successful. This will be fixed in anaconda-11.1.2.106. Created attachment 296907 [details]
anacdump.txt
reproduced without dmraid devices.
The trick seems to be:
- create custom partition layout
- reuse *exact* same partition layout already on disk
I agree that it is probably ok for the beta to go out like this, but is it too late to document this and point users to the updates.img here? Might save some new bug reports for something we have already fixed if nothing else. Another partitions re-using bug. Most likely unrelated: https://bugzilla.redhat.com/show_bug.cgi?id=246715 kistart reproducer from Xen guest with one disk 4GB initial install (autopart) --------------------------------------------------------------------- clearpart --all --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=528 --grow --maxsize=1056 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow --------------------------------------------------------------------- second install --------------------------------------------------------------------- part /boot --fstype ext3 --onpart xvda1 part pv.2 --noformat --onpart xvda2 volgroup VolGroup00 --noformat --useexisting --pesize=32768 pv.2 logvol swap --useexisting --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1056 logvol / --useexisting --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=2816 --------------------------------------------------------------------- note the --onpart options and that we're missing the clearpart command. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0397.html |