installed system qeth NIC name is too verbose

Bug #1526808 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
High
Dimitri John Ledkov

Bug Description

installed system qeth NIC name is too verbose

Specifically on s390x it came up as:

enccw0.0.0600

which is possibly too verbose, however it is definitive and trivial to understand for anyone with z/VM knowledge as this correlates with device hex address (aka 0x600 nic)

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1526808

tags: added: iso-testing
Revision history for this message
Martin Pitt (pitti) wrote :

In case you don't know yet: You want to start looking here:

  sudo udevadm test-builtin path_id /sys/class/net/eth0

which will say something like

D_PATH=ccwgroup-0.0.0600
ID_PATH_TAG=ccwgroup-0_0_0600

which will then result in
$ udevadm info /sys/class/net/eth0
P: /devices/qeth/0.0.0600/net/eth0
E: DEVPATH=/devices/qeth/0.0.0600/net/eth0
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME=enccw0.0.0600
E: ID_NET_NAME_MAC=enx02270a000012
E: ID_NET_NAME_PATH=enccw0.0.0600
E: ID_PATH=ccwgroup-0.0.0600
E: ID_PATH_TAG=ccwgroup-0_0_0600

Changed in systemd (Ubuntu):
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

So.

en -> is ethernet prefix. Given that there are other types of ccw devices that is ok.

cww -> is type of driver used, which is not necessary in the name.

0.0.0 -> i believe is redundant

600 -> is good, as that's the unique address that is used to configure thing in z/VM

I'm proposing to simply call them:

en600

Revision history for this message
Martin Pitt (pitti) wrote :

OK. I suppose "en600" might be too sloppy/short, but "enccw600" seems okay?

Care to open a ticket on https://github.com/systemd/systemd/issues so that we can find an upstreamable solution? We don't really want to introduce a permanent Ubuntu delta for this, especially as this will touch code. Thanks!

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Imho, enccw600 is confusing. FIrst of all, I have no idea why ccw code path is compiled on all architectures when this bus is only present on S/390.

Furthermore that's the only bus one can have ethernet devices (and dasd disk drives) on.

Thus all network nics end up with "ccw" in the name, which is weird. Thus I do want to drop the static prefix of ccw, which has no meaning (unlike e.g. letters in the PCI enumeration).

I've contacted original contributer of the ccw names, no response yet. Will propose upstream too.

Changed in systemd (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Dimitri John Ledkov (xnox) wrote :
tags: added: patch
Changed in systemd (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 228-4ubuntu2

---------------
systemd (228-4ubuntu2) xenial; urgency=high

  * Use shorter bus_id for ccw net-id interface names. LP: #1526808
  * Add a snippet to migrate existing network configuration to new names.

 -- Dimitri John Ledkov <email address hidden> Wed, 27 Jan 2016 19:01:12 +0000

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.