[UBUNTU 23.04] vlan interface lost after rebooting the operating system

[bugproxy]

---Problem Description---
[ubuntu 23.04] vlan interface lost after reboot of operating system

Contact Information = <email address hidden>

---uname output---
Linux a257ubut02 6.2.0-25-generic #25-Ubuntu SMP Fri Jun 16 16:15:36 UTC 2023 s390x s390x s390x GNU/Linux

Machine Type = 3932 - LA2 (LinuxONE 4)

---Steps to Reproduce---
 Hi,

In the test, I found the vlan interface will lost after I reboot the operating system, when the system boot up done, log in the system, restart the systemd-networkd service, the vlan interface can show up again.

test environment:
Linux distros: ubut 22.04 and 23.04, I used the ubut23.04 in the attached log
HW platform: LinuxONE 4 on DPM mode
network: set vNic using an OSA adapter as the backend adapter in trunk mode, I tried the adapter in access mode (assign the IP addr to enc device directly), no this issue.

I'll attach the systemd-networkd log (systemd-networkd-restart-network.log), here are some timestamps I did:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> Jul 17 04:15:10 -- reboot the operating system
After the system boot up down, login to the system, the vlan interface disappeared in the 'ip a' command

> Jul 17 04:25:02 -- restart the systemd-networkd service by 'sudo systemctl restart systemd-networkd.service' command
After restart service, the vlan interface appearred in the 'ip a' list, and the IP address assigned to the vlan is usable.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I opened the log and found some logs with issue point while IPLing, it shows the 'Lost carrier' in enc1000 (enc1000 is the physical device of the vlan interface), but I think there is no hardware issue in the lab, we are using the adapters for testing other distros like rhel, suse, and old ubut versions, like 20.04, all are Ok.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Link UP
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Gained carrier
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Link DOWN
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Lost carrier
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Could not create stacked netdev: No such device
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Failed
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Link UP
Jul 17 04:15:51 a257ubut02 systemd-networkd[1066]: enc1000: Gained carrier
Jul 17 04:15:52 a257ubut02 systemd-networkd[1066]: enc1000: Gained IPv6LL
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Could you please help to take a look, thanks~

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2023-08-01 10:38 EDT-------
===== Further testing by Yi Jie ============================================

Did some more test, I changed the network daemon from systemd-networkd to NetworkManager (still use netplan), the 'vlan interface lost after reboot' still there: reboot the os will lost the vlan interface, restart the NM service could shows up the vlan interface. In the NM log, it shows during the boot stage: manager: "(netplan-enc1000.1292) couldn't create the device: no support for VLANs on interface enc1000 of type Ethernet"

Here are some networkmanager service command output before and after 'restart nm service' as the comparison, and journalctl log file with operate timestamps:
>>>>>>>>>>>
journalctl -u NetworkManager > nm.log

timestamp: Jul 27 08:27 -> reboot the ubut os

timestamp: Jul 27 08:32 -> restart the nm service
>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>
run 'nmcli d' and 'nmcli c' before and after 'restart nm'

> before NM restart

ubuntu@a90ubut15:~$ nmcli d
DEVICE TYPE STATE CONNECTION
enc1000 ethernet connected netplan-enc1000
lo loopback connected (externally) lo

ubuntu@a90ubut15:~$ nmcli c
NAME UUID TYPE DEVICE
lo 2f1c6dd9-26ca-4276-a210-8bf61256322a loopback lo
netplan-enc1000 20393913-b9a9-3c3a-81cb-20f5840b309b ethernet enc1000
netplan-enc1000.1292 491497ea-36cb-3b96-ad99-6519b363483d vlan --

> after restart NM

ubuntu@a90ubut15:~$ nmcli d
DEVICE TYPE STATE CONNECTION
enc1000.1292 vlan connected netplan-enc1000.1292
enc1000 ethernet connected netplan-enc1000
lo loopback connected (externally) lo

ubuntu@a90ubut15:~$ nmcli c
NAME UUID TYPE DEVICE
netplan-enc1000.1292 491497ea-36cb-3b96-ad99-6519b363483d vlan enc1000.1292
lo 2f1c6dd9-26ca-4276-a210-8bf61256322a loopback lo
netplan-enc1000 20393913-b9a9-3c3a-81cb-20f5840b309b ethernet enc1000
>>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>>>>
I also compared the output of 'nmcli c show netplan-enc1000.1292' command before and after 'restart nm', found that the output of 'after the restart nm' not only include all the parameters in 'before the restart nm', and also plus the following parameters:

GENERAL.NAME: netplan-enc1000.1292
GENERAL.UUID: 491497ea-36cb-3b96-ad99-6519b363483d
GENERAL.DEVICES: enc1000.1292
GENERAL.IP-IFACE: enc1000.1292
GENERAL.STATE: activated
GENERAL.DEFAULT: yes
GENERAL.DEFAULT6: no
GENERAL.SPEC-OBJECT: --
GENERAL.VPN: no
GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/2
GENERAL.ZONE: --
GENERAL.MASTER-PATH: --
IP4.ADDRES...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2023-08-06 23:16 EDT-------
Hi Boris,

Thank you, may I know the ID or link to the ticket on Launchpad?