Unable to configure VLAN on an additional OSA interface

[bugproxy]

After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command.
However this results in the error message "RTNETLINK answers: File exists".

>----snip----
ip link add link ence530 name ence530.209 type vlan id 209
RTNETLINK answers: File exists
----snip----<

Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured.

Reproduction:

- Install a 18.04.1 server
- attach an additional OSA interface
- configure a VLAN using the ip command

[Dimitri John Ledkov (xnox)]

What's the output of: $ ip a ?

Also matching dmesg / syslog / journal?

[Frank Heimes (fheimes)]

Looks I can re-create this issue.
Just as a workaround, one may edit /etc/netplan/01-netcfg.yaml
do the configuration in a persistent way there and do a netplan apply:
$ sudo netplan apply --dryrun
$ sudo netplan apply

Please notice that you should have your system always on the latest level - means today in case of 18.04 it's 18.04.2 (incl. all patches) - 18.04.2 supersedes 18.04.1, but no need for a new install - just keep your system up-to-date with:
sudo apt update && sudo apt full-upgrade

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-07-29 11:17 EDT-------
(In reply to comment #5)
> What's the output of: $ ip a ?
>
> Also matching dmesg / syslog / journal?

root@m3515028:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: encbdf0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 02:3c:0f:00:00:46 brd ff:ff:ff:ff:ff:ff
inet 172.18.63.28/15 brd 172.19.255.255 scope global encbdf0
valid_lft forever preferred_lft forever
inet6 fe80::3c:fff:fe00:46/64 scope link
valid_lft forever preferred_lft forever
3: ence530: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 02:3c:0f:00:00:47 brd ff:ff:ff:ff:ff:ff

I'll attach the logs

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2019-07-29 11:19 EDT-------

[Frank Heimes (fheimes)]

Here are more details from my setup...

@Bug reporter, please share your details and logs as well!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-07-29 11:24 EDT-------
(In reply to comment #6)
> Looks I can re-create this issue.
> Just as a workaround, one may edit /etc/netplan/01-netcfg.yaml
> do the configuration in a persistent way there and do a netplan apply:
> $ sudo netplan apply --dryrun
> $ sudo netplan apply
>
> Please notice that you should have your system always on the latest level -
> means today in case of 18.04 it's 18.04.2 (incl. all patches) - 18.04.2
> supersedes 18.04.1, but no need for a new install - just keep your system
> up-to-date with:
> sudo apt update && sudo apt full-upgrade

To my knowledge, Ubuntu 18.04.1 is the LTS version and this the version we are testing against, so that's why the system is installed with that release. This is also visible in the image "Ubuntu kernel release cycle" on https://ubuntu.com/about/release-cycle

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2019-07-29 11:37 EDT-------
(In reply to comment #11)
> Here are more details from my setup...
>
> @Bug reporter, please share your details and logs as well!
>
>
Do you need more logs than the ones I had uploaded earlier? If so, which ones in particular?

[Frank Heimes (fheimes)]

Hi Michael,
looks like we added our comments and files in parallel.
I guess it's okay for now ...

[Dimitri John Ledkov (xnox)]

Unfortunately the logs are not that helpful, since VLAN additions are not printed in the dmesg/syslog/journal. I.e. one needs to bump udev logging to be more verbose.

Locally I can activate multiple NICs and like same vlan on both of them:

$ ip link | grep '^[0-9]'
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: encc000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
3: encc000.2653@encc000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
4: encc003: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
5: encc003.2653@encc003: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000

On bionic.

However, my NICs are 'Device is a OSD Express card (level: 0774)'

To get this further, we'd need to crank the logging up to see when, if any vlans, are created / added. However, it seems to me that I get no information from the kernel when vlan interfaces are added!

[Dimitri John Ledkov (xnox)]

Something is odd executing the command twice in a row does produce the same error message

$ sudo ip link add link encc003 name encc003.2653 type vlan id 2653
(exits zero, creates vlan interface)
$ sudo ip link add link encc003 name encc003.2653 type vlan id 2653
RTNETLINK answers: File exists
(because well, such vlan id indeed already exists)

But the difference is that I do have the vlan interface created/available, and the reporter does not. Unless it's a race.

[Dimitri John Ledkov (xnox)]

It is unclear how to reproduce the issue.

So far, I always have multiple VLANs configured and accessible. The only time I see errors similar to the ones from the reporter, is when the same vlan with the same name is configured multiple times in a row (which is an input/configuration error)

This bug will autoclose, unless better details are provided about the initial state of the machine / cards, current and prior VLAN configuration attempts. So far I cannot detect invalid behaviour, and the only errors that are produced are correct (i.e. when attempting to create a duplicate interface name)

[Launchpad Janitor (janitor)]

[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.]

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2021-01-21 04:47 EDT-------
Try Installation UBUNTU 18.04.02

add Vlan Interface to additional Qeth device works fine for me
encbd00: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 02:00:00:13:f0:1b brd ff:ff:ff:ff:ff:ff
inet 172.18.40.17/15 brd 172.19.255.255 scope global encbd00
valid_lft forever preferred_lft forever
inet6 fe80::ff:fe13:f01b/64 scope link
valid_lft forever preferred_lft forever
24: encb000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 02:00:00:15:0f:2c brd ff:ff:ff:ff:ff:ff
inet6 fe80::ff:fe15:f2c/64 scope link
valid_lft forever preferred_lft forever
25: encb00.202@encb000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:00:00:15:0f:2c brd ff:ff:ff:ff:ff:ff
inet6 fe80::ff:fe15:f2c/64 scope link
valid_lft forever preferred_lft forever
root@t83lp17:~# uname
Linux
root@t83lp17:~# uname -a
Linux t83lp17 4.15.0-132-generic #136-Ubuntu SMP Tue Jan 12 15:00:49 UTC 2021 s390x s390x s390x GNU/Linux
root@t83lp17:~# lsb
lsblk lsb_release
root@t83lp17:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04

root@t83lp17:~# uname -a
Linux t83lp17 4.15.0-132-generic #136-Ubuntu SMP Tue Jan 12 15:00:49 UTC 2021 s390x s390x s390x GNU/Linux
root@t83lp17:~#

Try to do an upgrade from UBUNTU18.04.01 as described from Frank,
work as well.

[Frank Heimes (fheimes)]

Thx for the re-test and update - with that I'm closing this ticket now.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2021-01-21 06:06 EDT-------
IBM Bugzilla status->closed, Fix Released

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2021-02-19 03:13 EDT-------
Just for the records:
A Firmware fix for the intermittent OSA Firmware issue that I suspected here is now available for z13 with D27I Bundle S103a.