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 438619[details]
installation log files (Server variant)
On installed system:
[root@system1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
HWADDR="52:54:00:12:34:56"
NM_CONTROLLED="yes"
ONBOOT="no"
Manual installation in virtual machine with network installation source.
I configured network just for an installation (as I did it with previous builds), that was dhcp configuration.
Not even network manager starts it automatically.
This is different behaviour in comparison to previous versions.
(In reply to comment #1)
> Created an attachment (id=438621) [details]
> installation log files (Client variant)
Marian, could you please post also /tmp/ifcfg.log grabbed from install environment before reboot? This is inconvenient, I should to send a patch for copying it to installed system as other log files.
Created attachment 438637[details]
anaconda.syslog extracted from the archive
It seems that NM is not loading ifcfg-rh plugin (see bug #620823), so network is enabled even for our initial ifcfg file containing ONBOOT=no, and therefore it is not enabled later which would be done by writing out ONBOOT=yes to ifcfg file.
Interesting. Network configuration dialog is not even displayed. Network is started in advance. When installer is asking 'Choose a Language' network is already up.
Maybe related to change introduced in Bug 617860 or something similar.
Yeah, so the issue here is that NM stopped shipping a deprecated config file (nm-system-settings.conf) in the RPM and now ships NetworkManager.conf, and I did not anticipate that the anaconda image creation code would need to be modified for this change as well.
anaconda-13.21.72/scripts/mk-images: cp -a $IMGPATH/etc/NetworkManager/nm-system-settings.conf $MBD_DIR/etc/NetworkManager
anaconda-13.21.72/scripts/upd-instroot:etc/NetworkManager/nm-system-settings.conf
*** Bug 625578 has been marked as a duplicate of this bug. ***
Comment 22releng-rhel@redhat.com
2010-11-10 19:52:59 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Created attachment 438619 [details] installation log files (Server variant) On installed system: [root@system1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE="eth0" HWADDR="52:54:00:12:34:56" NM_CONTROLLED="yes" ONBOOT="no" Manual installation in virtual machine with network installation source. I configured network just for an installation (as I did it with previous builds), that was dhcp configuration. Not even network manager starts it automatically. This is different behaviour in comparison to previous versions.