Bug 590525

Summary: NetworkManager did not pick up the active link
Product: Red Hat Enterprise Linux 6 Reporter: Qian Cai <qcai>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact:
Priority: high    
Version: 6.0   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-13 14:25:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Qian Cai 2010-05-10 04:20:55 UTC
Description of problem:
After installed from the RHEL6 Beta 1 DVD x86_64 ISO and upgraded the system to the snapshot 1, the NetworkManager did not pick up the active link which left no network in place by default. The workaround is to manually click the active link from the GUI.

Version-Release number of selected component (if applicable):

How reproducible:

Comment 1 Qian Cai 2010-05-10 05:54:26 UTC
# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Intel Corporation 82566DM-2 Gigabit Network Connection

# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+

Comment 2 Dan Williams 2010-05-12 18:40:49 UTC
Yeah, the issue is ONBOOT=no which is written by the installer.

This is because the install you did was not done using the network, and for security reasons networking is not started by default on reboot.  Had the install been done with the boot.iso or netinst, since network was used to install then networking would be enabled on reboot.  This is since fixed by allowing post-install configuration of network interfaces, though I don't know which bug that one is.

The Fedora counterpart is bug #498207.

Comment 3 David Cantrell 2010-05-13 14:25:41 UTC
The core problem here is being addressed by the patches for bug #520146.  Anaconda will offer users the ability to configure network devices on the target system during installation, so even in instances where you are performing a non-network installation, you can still configure network settings.

As for upgrading from beta 1 to snapshot 1, that's a non-issue.  First, we don't care about upgrades between testing releases.  Second, the behavior you are seeing is expected.  On upgrade, anaconda will honor the settings it finds in the ifcfg files on the system you are upgrading.

*** This bug has been marked as a duplicate of bug 520146 ***