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.
Created attachment 474174[details]
All anaconda log files from installs w/ eth0 or em1 specified in ks.cfg
Description of problem:
I installed RHEL6.1-20110117.n.1 Server on my Dell PowerEdge R710 and found that the network was not up after installation completed and the system rebooted. It turns out the network devices are named eth0..eth3 during install and em1..em4 after booting with the new biosdevname package which is new in RHEL 6.1.
Version-Release number of selected component (if applicable):
anaconda version 13.21.87 on x86_64
tree RHEL6.1-20110117.n.1
How reproducible:
Every time on this hardware
Steps to Reproduce:
1. Install new tree w/ biosdevname included
2.
3.
Actual results:
Expected results:
Additional info:
Created attachment 474174 [details] All anaconda log files from installs w/ eth0 or em1 specified in ks.cfg Description of problem: I installed RHEL6.1-20110117.n.1 Server on my Dell PowerEdge R710 and found that the network was not up after installation completed and the system rebooted. It turns out the network devices are named eth0..eth3 during install and em1..em4 after booting with the new biosdevname package which is new in RHEL 6.1. Version-Release number of selected component (if applicable): anaconda version 13.21.87 on x86_64 tree RHEL6.1-20110117.n.1 How reproducible: Every time on this hardware Steps to Reproduce: 1. Install new tree w/ biosdevname included 2. 3. Actual results: Expected results: Additional info: