Created attachment 415920 [details]
anaconda log file saved after the exception occurred
Description of problem:
After initiating a network install from media RHEL6.0-20100414.0-AP-x86_64-boot.iso including updates.img as of 2010-05-23 downloaded by the installer, anaconda aborts when the boot partition is set up on a disk on which a fully working F12 is currently installed. The disk layout includes the boot partition /dev/sda2 to which mount point /boot is assigned and an additional LVM partition for the remaining volumes. The file system type is ext4 in all cases. The anaconda log file issued after the unhandled exception is attached to this report.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start install of RHEL6 beta from boot.iso plus downloaded updates.img.
2. Set up disk layout.
3. Choose to reformat existing partition /dev/sda2 with mount point /boot
and file system type ext4 as before (F12).
Installer adopts chosen disk layout and proceeds.
- Disk layout is supposed to be recycled from a working F12 system
without changing any existing partition or volume apart from simply
reformatting them using the same file system types as before.
- Note that /dev/sda2 was not assigned any partition label when setting
up partitions from scratch during the preceding install of F12.
Can you please try again with a later build of anaconda? 126.96.36.199 is rather old at this point and I'm pretty sure this bug should be fixed.
Are the any public repositories where I can find updated boot media for the EL6 development tree?
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
*** This bug has been marked as a duplicate of bug 563526 ***