Bug 590525
Summary: | NetworkManager did not pick up the active link | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Qian Cai <qcai> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED DUPLICATE | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
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: | |
Embargoed: |
Description
Qian Cai
2010-05-10 04:20:55 UTC
# cat /etc/sysconfig/network-scripts/ifcfg-eth1 # Intel Corporation 82566DM-2 Gigabit Network Connection DEVICE=eth1 HWADDR=00:1E:4F:A8:AE:EF ONBOOT=no # cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ DEVICE=eth0 HWADDR=00:E0:4C:0B:16:0E ONBOOT=no 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. 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 *** |