Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJoachim Frieben
2010-05-23 05:46:38 UTC
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):
anaconda-13.21.20.5-1.el6.x86_64
How reproducible:
Always.
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).
Actual results:
Installer aborts.
Expected results:
Installer adopts chosen disk layout and proceeds.
Additional info:
- 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.
Are the any public repositories where I can find updated boot media for the EL6 development tree?
Comment 4RHEL Program Management
2010-05-27 14:16:08 UTC
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
inclusion.
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): anaconda-13.21.20.5-1.el6.x86_64 How reproducible: Always. 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). Actual results: Installer aborts. Expected results: Installer adopts chosen disk layout and proceeds. Additional info: - 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.