OSA/qeth inconsistent interface names

Bug #1822585 reported by Frank Heimes
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Invalid
High
bugproxy
s390-tools (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After doing an installation of an s390x system with disco where OSA devices are in use (means LPAR and z/VM) the device name of the default interface that is generated during the installation is file, for example:

ubuntu@s1lp15:~$ lszdev qeth | grep yes
qeth 0.0.c000:0.0.c001:0.0.c002 yes yes encc000

If another device is created (e.g. with the help of: sudo chzdev -e c003), it name is no longer based on the address, but it get's an 'eth?' name:

ubuntu@s1lp15:~$ lszdev qeth | grep yes
qeth 0.0.c000:0.0.c001:0.0.c002 yes yes encc000
qeth 0.0.c003:0.0.c004:0.0.c005 yes yes eth0

The coressponding 'ip a' line is:
9: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
(02:29:22 PM) jfh: link/ether 5a:2e:d8:c6:c1:03 brd ff:ff:ff:ff:ff:ff

After a 'sudo systemctl restart systemd-udev-trigger.service' it get's the correct name 'encc003':
9: encc003: <BROADCAST,MULTICAST>

Revision history for this message
Frank Heimes (fheimes) wrote :
Changed in ubuntu-z-systems:
importance: Undecided → Medium
assignee: nobody → bugproxy (bugproxy)
importance: Medium → High
bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-176566 severity-high targetmilestone-inin1904
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Mar 29 10:31:45 s1lp15 sudo[1126]: pam_unix(sudo:session): session closed for user root
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:account): account ubuntu has password changed in future
Mar 29 10:32:02 s1lp15 sudo[1144]: ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/chzdev qeth -e c003
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
Mar 29 10:32:02 s1lp15 kernel: qdio: 0.0.c005 OSA on SC bb1 using AI:1 QEBSM:0 PRI:1 TDD:1 SIGA: W AP
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: Using default interface naming scheme 'v240'.
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: Could not set Alias=, MACAddress= or MTU= on eth0: Resource temporarily unavailable
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: eth0: Could not apply link config, ignoring: Resource temporarily unavailable
Mar 29 10:32:02 s1lp15 systemd-udevd[1146]: Process 'vlan-network-interface UDEV' failed with exit code 1.
Mar 29 10:32:02 s1lp15 kernel: qeth.6adf49: 0.0.c003: The device represents a Bridge Capable Port
Mar 29 10:32:02 s1lp15 kernel: qeth.cc0c57: 0.0.c003: MAC address 82:80:10:91:6a:a4 successfully registered on device eth0
Mar 29 10:32:02 s1lp15 kernel: qeth.26d434: 0.0.c003: Device is a OSD Express card (level: 0774)
                               with link type OSD_10GIG.
Mar 29 10:32:02 s1lp15 kernel: qeth.f02020: 0.0.c003: QDIO data connection isolation is deactivated
Mar 29 10:32:02 s1lp15 networkd-dispatcher[631]: WARNING:Unknown index 8 seen, reloading interface list
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:session): session closed for user root

systemd-udevd tries to rename the device, before kernel says it's ok to do so. Note that device is a Bridge Capable Port. So something is racy in the chzdev -e codepath.

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Confirmed
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2019-04-12 05:28 EDT-------
I installed Ubuntu 19.04 on my z/VM guest:

root@s8345038:~# uname -a
Linux s8345038 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:57:17 UTC 2019 s390x s390x s390x GNU/Linux
root@s8345038:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
VERSION_ID="19.04"
<snip>

I configured a new device:

root@s8345038:~# chzdev -e -a qeth e400
Configuring devices in the active configuration only
QETH device 0.0.e400:0.0.e401:0.0.e402 configured

and its shown in ip a output as expected, with correct name:

root@s8345038:~# ip a
<snip>
3: ence400: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:a2:2d:00:05:81 brd ff:ff:ff:ff:ff:ff

journalctl -x output shows correct processing order: first qeth, then systemd:

Apr 12 11:16:17 s8345038 kernel: qeth.e804c4: 0.0.e400: Priority Queueing not supported
Apr 12 11:16:17 s8345038 kernel: qdio: 0.0.e402 OSA on SC 12 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A
Apr 12 11:16:17 s8345038 systemd-udevd[1312]: Using default interface naming scheme 'v240'.
Apr 12 11:16:17 s8345038 systemd-udevd[1312]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 12 11:16:17 s8345038 kernel: qeth.6adf49: 0.0.e400: The device represents a Bridge Capable Port
Apr 12 11:16:17 s8345038 kernel: qeth.cc0c57: 0.0.e400: MAC address 02:a2:2d:00:05:81 successfully registered on device eth0
Apr 12 11:16:17 s8345038 kernel: qeth 0.0.e400 ence400: renamed from eth0
Apr 12 11:16:17 s8345038 kernel: qeth.26d434: 0.0.e400: Device is a OSD Express card (level: 0774)
with link type OSD_10GIG.
Apr 12 11:16:17 s8345038 kernel: qeth.f02020: 0.0.e400: QDIO data connection isolation is deactivated
Apr 12 11:16:17 s8345038 systemd-networkd[329]: eth0: Interface name change detected, eth0 has been renamed to ence400.
Apr 12 11:16:17 s8345038 networkd-dispatcher[660]: WARNING:Unknown index 3 seen, reloading interface list
Apr 12 11:16:17 s8345038 systemd-udevd[1326]: Using default interface naming scheme 'v240'.

So I cannot see this problem here.

Revision history for this message
Frank Heimes (fheimes) wrote :

I just tried with the very latest kernel from disco proposed:

ubuntu@s1lp15:~$ uname -r
5.0.0-11-generic
ubuntu@s1lp15:~$ lszdev qeth | head -n 5
TYPE ID ON PERS NAMES
qeth 0.0.c000:0.0.c001:0.0.c002 yes yes encc000
qeth 0.0.c003:0.0.c004:0.0.c005 yes yes encc003
qeth 0.0.c006:0.0.c007:0.0.c008 no no
qeth 0.0.c009:0.0.c00a:0.0.c00b no no
ubuntu@s1lp15:~$ sudo chzdev -e c006
[sudo] password for ubuntu:
QETH device 0.0.c006:0.0.c007:0.0.c008 configured
ubuntu@s1lp15:~$ lszdev qeth | head -n 5
TYPE ID ON PERS NAMES
qeth 0.0.c000:0.0.c001:0.0.c002 yes yes encc000
qeth 0.0.c003:0.0.c004:0.0.c005 yes yes encc003
qeth 0.0.c006:0.0.c007:0.0.c008 yes yes eth0
qeth 0.0.c009:0.0.c00a:0.0.c00b no no
ubuntu@s1lp15:~$

Do you have the option in your system to enable even one or two more qeth devices ?

Revision history for this message
Frank Heimes (fheimes) wrote :

Please can you share the output of "lszdev qeth", too?

And is your system connected to a VLAN - means do you have a VLAN device in your system?

Apr 12 06:05:45 s1lp15 kernel: qeth.e804c4: 0.0.c006: Priority Queueing not supported
Apr 12 06:05:45 s1lp15 kernel: qdio: 0.0.c008 OSA on SC bb4 using AI:1 QEBSM:0 PRI:1 TDD:1 SIGA: W AP
Apr 12 06:05:45 s1lp15 systemd-udevd[869]: Using default interface naming scheme 'v240'.
Apr 12 06:05:45 s1lp15 systemd-udevd[869]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 12 06:05:45 s1lp15 systemd-udevd[869]: Could not set Alias=, MACAddress= or MTU= on eth0: Resource temporarily unavailable
Apr 12 06:05:45 s1lp15 systemd-udevd[869]: eth0: Could not apply link config, ignoring: Resource temporarily unavailable
Apr 12 06:05:45 s1lp15 systemd-udevd[869]: Process 'vlan-network-interface UDEV' failed with exit code 1.
Apr 12 06:05:45 s1lp15 kernel: qeth.6adf49: 0.0.c006: The device represents a Bridge Capable Port
Apr 12 06:05:45 s1lp15 kernel: qeth.cc0c57: 0.0.c006: MAC address 9e:c3:44:57:ac:28 successfully registered on device eth0
Apr 12 06:05:45 s1lp15 kernel: qeth.26d434: 0.0.c006: Device is a OSD Express card (level: 0774)
                               with link type OSD_10GIG.
Apr 12 06:05:45 s1lp15 kernel: qeth.f02020: 0.0.c006: QDIO data connection isolation is deactivated
Apr 12 06:05:45 s1lp15 networkd-dispatcher[570]: WARNING:Unknown index 11 seen, reloading interface list
Apr 12 06:05:45 s1lp15 dnsmasq[809]: reading /etc/resolv.conf
Apr 12 06:05:45 s1lp15 dnsmasq[809]: using nameserver 127.0.0.53#53
Apr 12 06:05:45 s1lp15 sudo[864]: pam_unix(sudo:session): session closed for user root

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2019-04-12 09:56 EDT-------
I added a self-defined vlan device

root@s8345038:~# lszdev qeth
TYPE ID ON PERS NAMES
qeth 0.0.bdf0:0.0.bdf1:0.0.bdf2 yes yes enccw0.0.f5f0
qeth 0.0.e400:0.0.e401:0.0.e402 yes no ence400
qeth 0.0.e413:0.0.e414:0.0.e415 no no

root@s8345038:~# ip link add dev ence400.201 link ence400 type vlan id 201
root@s8345038:~# ip a
<snip>
3: ence400: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:a2:2d:00:05:81 brd ff:ff:ff:ff:ff:ff
4: ence400.201@ence400: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:a2:2d:00:05:81 brd ff:ff:ff:ff:ff:ff

Now use chzdev to define the e413 device, and it works:

root@s8345038:~# lszdev qeth
TYPE ID ON PERS NAMES
qeth 0.0.bdf0:0.0.bdf1:0.0.bdf2 yes yes enccw0.0.f5f0
qeth 0.0.e400:0.0.e401:0.0.e402 yes no ence400
qeth 0.0.e413:0.0.e414:0.0.e415 no no
root@s8345038:~# chzdev -e e413
QETH device 0.0.e413:0.0.e414:0.0.e415 configured
root@s8345038:~# lszdev qeth
TYPE ID ON PERS NAMES
qeth 0.0.bdf0:0.0.bdf1:0.0.bdf2 yes yes enccw0.0.f5f0
qeth 0.0.e400:0.0.e401:0.0.e402 yes no ence400
qeth 0.0.e413:0.0.e414:0.0.e415 yes yes ence413

Maybe the difference is the kernel. I can try to update it to the -11 kernel, hope that works...

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2019-05-10 02:43 EDT-------
@Heinz-Werner: when I tested with pre-ga there was no kernel update to install available from our update servers. Will try soon with GA version that we have available.

Revision history for this message
bugproxy (bugproxy) wrote :
Download full text (5.2 KiB)

------- Comment From <email address hidden> 2019-05-10 05:08 EDT-------
I installed a new 19.04, which came with kernel -13. I ran the same tests as before, and did not see any problem. Please see my complete log below for a replay.

root@s8345042:~# uname . -a
Linux s8345042 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:58:28 UTC 2019 s390x s390x s390x GNU/Linux

root@s8345042:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="19.04 (Disco Dingo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 19.04"
VERSION_ID="19.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

root@s8345042:~# chzdev -e -a qeth e406
Configuring devices in the active configuration only
QETH device 0.0.e406:0.0.e407:0.0.e408 configured

root@s8345042:~# ip a
<snip>
3: ence406: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:a2:2d:00:06:70 brd ff:ff:ff:ff:ff:ff

journalctl -x output, first qeth, then systemd:
----------------------
May 10 10:50:37 s8345042 kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=1, erc=4, rsid=12
May 10 10:50:37 s8345042 kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=1, erc=4, rsid=13
May 10 10:50:37 s8345042 kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=1, erc=4, rsid=14
May 10 10:50:59 s8345042 kernel: qeth.e804c4: 0.0.e406: Priority Queueing not supported
May 10 10:50:59 s8345042 kernel: qdio: 0.0.e408 OSA on SC 14 using AI:1 QEBSM:1 PRI:1 TDD:1 SIGA: W A
May 10 10:50:59 s8345042 systemd-udevd[1115]: Using default interface naming scheme 'v240'.
May 10 10:50:59 s8345042 systemd-udevd[1115]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 10 10:50:59 s8345042 kernel: qeth.6adf49: 0.0.e406: The device represents a Bridge Capable Port
May 10 10:50:59 s8345042 kernel: qeth.cc0c57: 0.0.e406: MAC address 02:a2:2d:00:06:70 successfully registered on device eth0
May 10 10:50:59 s8345042 kernel: qeth 0.0.e406 ence406: renamed from eth0
May 10 10:50:59 s8345042 kernel: qeth.26d434: 0.0.e406: Device is a OSD Express card (level: 0774)
with link type OSD_10GIG.
May 10 10:50:59 s8345042 kernel: qeth.f02020: 0.0.e406: QDIO data connection isolation is deactivated
May 10 10:50:59 s8345042 systemd-networkd[327]: eth0: Interface name change detected, eth0 has been renamed to ence406.
May 10 10:50:59 s8345042 networkd-dispatcher[663]: WARNING:Unknown index 3 seen, reloading interface list
May 10 10:50:59 s8345042 systemd-udevd[1125]: Using default interface naming scheme 'v240'.

root@s8345042:~# lszdev qeth
TYPE ID ON PERS NAMES
qeth 0.0.bdf0:0.0.bdf1:0.0.bdf2 yes yes enccw0.0.f5f0
qeth 0.0.e406:0.0.e407:0.0.e408 yes no ence406

root@s8345042:~# vmcp att e40c-e40e \*
E40C-E40E ATTACHED TO S8345042

root@s8345042:~# chzdev -a -e qeth e40c
Configuring devices in the active configuration only
QETH device 0.0.e40c:0.0.e40d:0.0.e40e configured

root@s8345042:~# ip a
<snip>
3: ence406: <BROADCAST...

Read more...

Revision history for this message
Frank Heimes (fheimes) wrote :

Obviously fixed with release kernel, didn't saw it afterwards anymore, hence closing.

Changed in s390-tools (Ubuntu):
status: New → Invalid
Changed in ubuntu-z-systems:
status: Confirmed → Invalid
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2019-05-15 10:16 EDT-------
IBM bugzilla status -> closed, Not reproducable anymore by Canonical

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.