The naming currently is ethXX where XX is a sequential number that does not 
correlate with the port on the front panel. For example, eth0 will sometimes 
correlate with port 30, and on the next reboot it will be port 6.
After the patch is installed, the devices are named enp3s0pXX where XX 
correlates with the panel names, for example enp3s0p1 correlates to port 1.

I am not aware of any other devices that make use of phys_port_name
patterns.

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

Title:
  udev netdev naming does not work with mellanox switches

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Yakkety:
  Incomplete

Bug description:
  The current packaged systemd for Yakkety does not have the Mellanox
  netdev udev naming set for systemd patch installed
  (https://github.com/systemd/systemd/commit/4887b656c22). The current
  version for zesty does. I installed the ppa for this on to my Yakkety
  switch and rebooted and the devices are properly named.

  SRU TEST CASE:
    * (To be filled out by Luke)

  REGRESSION POTENTIAL:
  This changes the network device names for an unknown set of devices (those 
which have a "phys_port_name" sysfs attribute), which can lead to 
unbootable/inaccessible existing systems. @Luke: Is this only being used by 
Mellanox drivers in yakkety's kernels? Which other drivers expose this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1644355/+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