Comment 9 for bug 2022030

Hi Frank,

Thanks for the investiaging.

Yes, Wei is my colleague, contacted with him and his trial was on a similar system and almost same configuraiton of my testing this time.

And following you and Wei's last comments in 1996007, I reproduced the same scenario w/ the only change is set the network interface from trunk mode to access mode (leave the 'vlan id (optional)' field blank). In this case, the IP addr did not lost. (Acturally, in the previous failed case, the enc** interface was exist either, the lost interface was the vlan interface, and the IP addr was assigned to the vlan in trunk mode, so the IP addr was lost as well.)

This is the yaml configure file I use access mode adapter today:

*************************************************************
ubuntu@ibm:~$ cat /etc/netplan/00-installer-config.yaml
# This is the network config written by 'subiquity'
network:
  ethernets:
    enc1000:
      addresses:
      - 10.20.92.248/24
      gateway4: 10.20.92.254
      nameservers:
        addresses:
        - 10.20.0.2
  version: 2
********************************************************

From the behavior, I understand your comment: "That let's me assume that it's related to the current switch configuration.", but the strange is, I installed ubuntu using trunk mode network from the older ubuntu versions ago, the installation always successfully, ip assigned to the vlan interface, no lost.

As a comparation, I installed an ubuntu 20.04 using trunk mode today, the vlan interface remained after the installation, this issue (vlan interface lost) seems only exist in 22.04 and 23.04.

I'll attach the install logs I tried today, hope they helps.

install 23.04 in access mode, success --> 2304-access-success-installer.tar
install 20.04 in truck mode, success --> 2004-trunk-success-installer.tar
install 23.04 in trunk mode, vlan interface lost --> please refer comment #7

Thanks.