[Bug 594250] New: udev persistent net interface gets renamed on first boot after upgrade
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c0 Summary: udev persistent net interface gets renamed on first boot after upgrade Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: jsrain@novell.com Found By: Customer Blocker: --- Suspected packages: udev-146-3.3.1.i586 or sysconfig-0.72.6-2.5.1.i586 Starting from OpenSuSE 10.3 I upgrade to 11.2. Just before rebooting into 11.2 I inspect /etc/udev/rules.d/70-persistent-net.rules and it is the same as it was before I started, for example (excluding comments): SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:6e:40:7e:25", KERNEL=="eth*", NAME="eth0" It reboots and everything is fine on most machines, but on about 10% of them eth0 does not come up; instead we get eth1. The most recent instance happened on a compute cluster node where we put some work into making them identical, and other such mishaps occurred on systems virtually identical to others that got upgraded without incident. To the above line a script appended this one: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:6e:40:7e:25", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" On a machine with multiple NICs, if there's a problem then each NIC will get a new line and name. On the machines that didn't have a problem a line similar to the above *replaced* the original, i.e. 'ACTION=="add"' and 'ATTR{type}=="1"' are inserted, plus the 10.3 comment "converted netiface rule..." is replaced by the new style that gives the PCI bus ID. (These machines had SuSE 10.1 on them before 10.3.) The comment in 70-persistent-net.rules says it was rewritten by /etc/sysconfig/network/scripts/convert_persistent_name_rules . We're trying to do as many upgrades as possible in the middle of the night, working from home, so as to work around our users, and needless to say, it's a problem when one of the machines won't come up after the upgrade. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |kasievers@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c1 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jimc@math.ucla.edu --- Comment #1 from Kay Sievers <kasievers@novell.com> 2010-04-07 06:39:29 UTC --- Please attach the rules file from a machine where this goes wrong. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c2 --- Comment #2 from James Carter <jimc@math.ucla.edu> 2010-04-07 07:14:35 UTC --- Created an attachment (id=352775) --> (http://bugzilla.novell.com/attachment.cgi?id=352775) Rules file from 10.3 before upgrade -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c3 James Carter <jimc@math.ucla.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jimc@math.ucla.edu | --- Comment #3 from James Carter <jimc@math.ucla.edu> 2010-04-07 07:25:39 UTC --- Created an attachment (id=352777) --> (http://bugzilla.novell.com/attachment.cgi?id=352777) After the upgrade a line is appended that changes the interface name. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c4 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kasievers@novell.com |mt@novell.com --- Comment #4 from Kay Sievers <kasievers@novell.com> 2010-04-07 09:20:08 UTC --- This rule is not properly converted, ATTRS can not work, it needs to be ATTR, and it misses keys udev expects. Passing over to sysconfig. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c5 --- Comment #5 from James Carter <jimc@math.ucla.edu> 2010-04-08 04:57:19 UTC --- Thanks for the quick response. The pre-conversion rule does get recognized on SuSE 10.3, I think because ATTRS refers to the event (subject) device or its parents and the event device does have a MAC address. However, my concern is that in the transition to SuSE 11.2, most of the time the new rule replaces the one from 10.3, but occasionally it is appended with a new interface name, breaking things. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c6 Marius Tomaschewski <mt@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #6 from Marius Tomaschewski <mt@novell.com> 2010-04-12 11:16:08 UTC --- This bug is a dupplicate of bug 546575 and released for 11.2 as update -- changelog: * Mo Nov 23 2009 mt@suse.de - Fixed typo in convert_persistent_name_rules script causing to generate persistent name rules on update, not matching MAC address (bnc#546575). The easiest/best solution is to add the 11.2 update repository as an additional installation source during the installation/update from 10.3. This causes, that the fixed packages make the conversions instead of the GA version, that contains the typo. Using this way solves a lot of another problems with post-release fixes to update routines -- also in another packages. When it already happened, manual correction of the rule is required: - remove the invalid rule (contains incorrect ATTRS, correct NAME) - set NAME= in the additional rule generated by udev (same MAC address correct ATTR, but a different interface name, eth1 here) to the NAME as in the invalid rule. - reboot alternatively: use yast2 network and reconfigure. *** This bug has been marked as a duplicate of bug 546575 *** http://bugzilla.novell.com/show_bug.cgi?id=546575 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=594250 http://bugzilla.novell.com/show_bug.cgi?id=594250#c7 --- Comment #7 from James Carter <jimc@math.ucla.edu> 2010-04-12 20:39:41 UTC --- @Marius, thanks for the suggestions. The strange thing is, we do add the update repo when doing the upgrade, and I can prove that the most recently upgraded machine (where the problem occurred) received sysconfig-0.72.6-2.5.1.i586 as part of the upgrade and not from a subsequent online update. After upgrading we verify installation of our special Math packages and then do update again, and it reports "nothing to do", which is true. Also, all but one or two of these machines is being upgraded from SuSE 10.3 and had 10.1 on it before that, and so the same failure should have occurred on every one, but it didn't. I have the impression that there are two scripts that update persistent interface names, but I haven't been able to track down the second one. I think that when setting up for an upgrade I'm going to preemptively fix 70-persistent-net.rules and hope that it will not be fixed recursively. Yes, we do have /etc/udev/rules.d/30-net_persistent_names.rules.disabled on both affected and unaffected machines, left over from SuSE 10.1 which most of them had before 10.3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com