Bug 246529
| Summary: | on a system with two network cards, kudzu switches cards at boot time | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | pf <pf-bugzilla-070701> |
| Component: | kudzu | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 7 | CC: | rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-07-02 20:38:48 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
pf
2007-07-02 20:33:11 UTC
HWADDR= is required for stable device mapping. I think that if this behavior has changed from previous versions of fedora, at least this change should be documented. Not sure what you mean - it's been this way since roughly FC3/FC4 (when udev started being used to load modules.) Most of my servers are FC3 (FC4 didn't work on most of them, so I stopped upgrading). On FC3 you only had to change modprobe.conf entries like "alias eth0 e100". Changing the assignment ethx to driver there, you changed which card was used on each eth, and this assignment remained stable (I checked, I have a udev command on these systems). Now, modprobe.conf continues to have entries like "alias eth0 e100", but this statement is not used to assign drivers to the cards. You now say I have to use HWADDR on ifcfg to make the setup stable. I found no reference to this procedure in the documentation. Also, if the new procedure is to change the ifcfg to assign eth to cards, then why does modprobe.conf continue having statements like "alias eth0 e100"? Perhaps these statements should be modified to "alias eth e100" or any generic mapping? Now I remember another problem that is related with this stuff: On systems with redhat 7, if a network card failed I just swapped it with another one of the same type, and the server was ready to go. On fedora systems, if I do this then the setup of the card is destroyed at startup, so I had to backup the setup and restore it after the first restart. Now I think this is related if the hardware detection uses HWADDR and not the card type to identify network cards. The issue is that the 'alias ...' isn't used at all; modules are loaded on bootup, in parallel, by udev. Since they're loaded in parallel, which interface initializes first depends on timing within the drivers, and can change. Hence, there needs to be additional information to have perisitent ordering - since we already used HWADDR, and all the config tools (including anaconda) write it, it was the logical choice. However, it doesn't necessarily get applied on upgrade (as we don't rewrite config files there.) Now I understand the process. Thanks. |