> Any reason you cannot move to new naming scheme?

Please remember that this report may represent a large number of
affected users, most of whom are absent from this discussion. We want to
avoid regressing stable release Ubuntu users as much as possible, and
this generally means that we cannot break them during the lifetime of a
supported Ubuntu release.

I think the first question that needs to be answered would be: any
reason you cannot fix the original bug without breaking existing users?

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.

  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70

Status in OEM Priority Project:
Status in systemd package in Ubuntu:

Bug description:
  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 

  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [    4.518507] igb 0000:04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [    4.565081] igb 0000:07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with 
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to