Bug 514262
| Summary: | Seemingly random NIC enumeration in RHEL6 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Gary Case <gcase> | ||||||
| Component: | anaconda | Assignee: | David Cantrell <dcantrell> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0 | CC: | dcbw, mflitter, notting | ||||||
| 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-01-23 01:28:13 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Gary Case
2009-07-28 15:41:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Created attachment 355429 [details]
sosreport of system with eth0, eth4-7
Original enumeration comes from anaconda. How reproducible: Each boot post-install keeps the same unusual NIC ordering Steps to Reproduce: 1. Install RHEL6 on a system with a 4-port NIC and an onboard NIC 2. Reboot after install 3. Observe the strange NIC ordering Actual results: Holes in NIC naming sequence Expected results: NICs enumerated in order Additional info: Notting, I'll try a few more installs to see if anaconda keeps this same ordering. -Gary If I run ifconfig -a on the terminal during install, it shows eth0-eth4. After the reboot, I get eth0 and eth4-eth7. What's the content of /etc/udev/rules.d/70-persistent-net.rules (and/or /etc/sysconfig/network-scripts/ifcf-g*) on the installed system 1) when anaconda finishes 2) after rebooting ? Okay. It looks like the ifcfg-* files are correct post-boot. They're called eth0-eth4 and their contents name them as eth0-eth4. It's the persistent net rules file and the output of NetworkManager that's wacky. I'm attaching a tarball with all the files. Created attachment 355460 [details]
udev and ifcfg-eth config files, captured post-install
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:00:00:00:00:00", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"
Yeah, that's broken.
Let me know how it goes; some devices may not have MAC addresses until they are given one. In this case, it's best to write udev rules to assign a MAC to the device based on other hardware attributes (like pci bus location, USB serial number, etc), if it doesn't have the capability to store its MAC address in NVRAM. Thus the MAC address is available to NetworkManager and ifup/ifdown. *** This bug has been marked as a duplicate of bug 450590 *** *** Bug 839313 has been marked as a duplicate of this bug. *** |