** Description changed:

  [Impact]
  Interfaces associated with Huawei "hinic" PCI adapters will not be assigned 
predictable names[*] and instead remain using the kernel names (e.g. eth0). 
This can lead to races where the interface names are not the same on every 
boot. For example, in a system with both 2-port hinic and 2-port igb devices, 
the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic 
before igb loaded. But if igb completes loading first, the hinic interfaces 
would be eth2 & eth3.
  
  [*]
  
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
  
  [Test Case]
- grep ^eth /proc/net/dev
+ lsmod | grep hinic
+ grep eth /proc/net/dev
  
  [Fix]
  There's an upstream fix that properly associates the hinic interfaces with 
their PCI devices, providing udev with the info it needs to generate a 
predictable name.
  
  [Regression Risk]
  The big regression risk here is with existing bionic installs w/ hinic 
devices. They will be currently using "eth" names by default, and this change 
will cause those names to change to "enP" names after upgrade. However, in only 
certain configs are those "eth" names reliable (e.g. only NIC in the system is 
a hinic plug-in card). It sucks to introduce such a change in a stable release 
- but users will be bitten by this when they upgrade or transition to the HWE 
kernel anyway if we don't.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783138

Title:
  hinic interfaces aren't getting predictable names

Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Interfaces associated with Huawei "hinic" PCI adapters will not be assigned 
predictable names[*] and instead remain using the kernel names (e.g. eth0). 
This can lead to races where the interface names are not the same on every 
boot. For example, in a system with both 2-port hinic and 2-port igb devices, 
the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic 
before igb loaded. But if igb completes loading first, the hinic interfaces 
would be eth2 & eth3.

  [*]
  
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

  [Test Case]
  lsmod | grep hinic
  grep eth /proc/net/dev

  [Fix]
  There's an upstream fix that properly associates the hinic interfaces with 
their PCI devices, providing udev with the info it needs to generate a 
predictable name.

  [Regression Risk]
  The big regression risk here is with existing bionic installs w/ hinic 
devices. They will be currently using "eth" names by default, and this change 
will cause those names to change to "enP" names after upgrade. However, in only 
certain configs are those "eth" names reliable (e.g. only NIC in the system is 
a hinic plug-in card). It sucks to introduce such a change in a stable release 
- but users will be bitten by this when they upgrade or transition to the HWE 
kernel anyway if we don't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions

-- 
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