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.
DescriptionAlexander Todorov
2010-11-25 13:16:15 UTC
+++ This bug was initially created as a clone of Bug #647462 +++
From the original bug report:
--- Additional comment from clumens on 2010-10-28 17:12:43 EEST ---
Please attach /tmp/ifcfg.log (or /var/log/anaconda.ifcfg.log after rebooting) to this bug report. It would also be helpful to know what kind of install this was.
... skip ...
--- Additional comment from clumens on 2010-10-28 20:24:49 EEST ---
Okay, we don't copy that file to the installed system after installation is complete. So, before rebooting but while anaconda is sitting at the final screen, please switch to tty2 and grab /tmp/ifcfg.log and attach that to this bug report.
That file tells us what anaconda is going to write to everything in /etc/sysconfig/network-scripts, which seems like it would be pretty helpful in debugging this problem.
Comment 1Alexander Todorov
2010-11-25 13:17:31 UTC
Please copy /tmp/ifcfg.log to /var/log/anaconda.ifcfg.log in the installed system. This can help in testing and debugging problems.