[Bug 2022030] Re: vlan network device lost after the ubuntu 23.04 install complete
Frank Heimes
2022030 at bugs.launchpad.net
Thu Jun 1 16:30:57 UTC 2023
Hello, it looks to me that you haven't done a default installation.
A default installation in a vlan network environment leads to such a netplan yaml file (/etc/netplan/00-installer-config.yaml):
--------%<----------------%<----------------%<----------------%<--------
# This is the network config written by 'subiquity'
network:
ethernets:
encc000: {}
version: 2
vlans:
encc000.2653:
addresses:
- 10.245.236.15/24
gateway4: 10.245.236.1
id: 2653
link: encc000
nameservers:
addresses:
- 10.245.236.1
--------%<----------------%<----------------%<----------------%<--------
(I just did an installation from scratch, trying to reproduce.)
Your is this:
--------%<----------------%<----------------%<----------------%<--------
# This is the network config written by 'subiquity'
network:
ethernets:
enc1000: {}
version: 2
vlans:
enc1000.1300:
addresses:
- 10.20.103.65/24
routes:
- to: default
via: 10.20.103.254
id: 1300
link: enc1000
nameservers:
addresses:
- 10.20.0.2
--------%<----------------%<----------------%<----------------%<--------
Notice 'gateway4' vs 'routes ...'
Do you have an openvswitch (ovs) in your environment? If so, how is it setup?
Have you done any other network related (re-)configurations?
Can you please perform a default installation w/o ovs?
Could you also share the output of:
$ lszdev --online
Is your system a DPM system?
In case yes, can you also share:
sudo lszdev --auto-conf
Can you please share the exact settings that you've specified in your early network configuration step?
So after:
"Attempt interactive netboot from a URL?"
in the console?
(
like in my case:
Attempt interactive netboot from a URL?
yes no (default yes):
yes
Available qeth devices:
0.0.c000 0.0.c003 0.0.c006
zdev to activate (comma separated, optional):
c000
[ 83.508886] lcs: Loading LCS driver
[ 83.576712] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 83.578446] qeth: register layer 2 discipline
[ 83.579381] qeth 0.0.c000: CHID: 14c CHPID: c0
[ 83.587240] qeth 0.0.c002: qdio: OSA on SC bae using AI:1 QEBSM:0 PRI:1 TDD:1 SIGA: W
[ 83.612746] qeth 0.0.c000: Device is a OSD Express card (level: 0777)
[ 83.612746] with link type OSD_10GIG.
[ 83.613174] qeth 0.0.c000: The device represents a Bridge Capable Port
[ 83.614065] qeth 0.0.c000: MAC address 9e:30:60:41:bf:f8 successfully registered
[ 83.615392] qeth 0.0.c000 encc000: renamed from eth0
A manual update of the initial RAM-disk is required.
QETH device 0.0.c000:0.0.c001:0.0.c002 configured
Note: The initial RAM-disk must be updated for these changes to take effect:
- QETH device 0.0.c000:0.0.c001:0.0.c002
Two methods available for IP configuration:
* static: for static IP configuration
* dhcp: for automatic IP configuration
static dhcp (default 'dhcp'):
static
ip:
10.245.236.15
netmask (default 255.255.255.0):
gateway (default 10.245.236.1):
dns (default 10.245.236.1):
vlan id (optional):
2653
Available interfaces:
encc000
device (default encc000):
encc000
http://cdimage.ubuntu.com/releases/lunar/release/ubuntu-23.04-live-server-s390x.iso (default)
url:
http_proxy (optional):
)
Also also what you have specified in the semi-graphical (subiquity)
installer screen? (with having the network configured at 'interactive
netboot', one can usually skip any further config in the installer
screen regarding network.)
Please would you also share the entire /var/log/installer folder? That
would allow further diagnostics.
The "systemd-networkd-wait-online.se tart running messages", like:
M[K[[0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for Wait for k to be Configured (6s / no limit)
M[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for Wait for k to be Configured (6s / no limit)
M[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for Wait for k to be Configured (7s / no limit)
M[K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is running for Wait for k to be Configured (7s / no limit)
usually indicate that there is an issue with the network (connectivity).
The interface(s) that were configured, probably do not all have proper connectivity / or no link.
'systemd-networkd-wait-online' (a oneshot system service) waits for the network to be configured. By default, it will wait for all links it is aware of and which are managed by systemd-networkd.service to be fully configured or failed, and for at least one link to be online.
https://www.freedesktop.org/software/systemd/man/systemd-networkd-wait-online.service.html
To change this (default) behavior of 'systemd-netword-wait-online', and preventing the system from waiting on a network connection (btw. it waits for up to 2 minutes), there are a few options like:
1) adding 'optional: true' below an interface the system should not wait for:
encc000:
optional: true
2) or to 'ExecStart' your systemd-networkd-wait-online.service like this:
[Service]
ExecStart=
ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --any
... just to name two.
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/2022030
Title:
vlan network device lost after the ubuntu 23.04 install complete
Status in Ubuntu on IBM z Systems:
Incomplete
Status in netplan.io package in Ubuntu:
New
Status in subiquity package in Ubuntu:
New
Bug description:
ubuntu at ibm:~$ cat /etc/os-release
PRETTY_NAME="Ubuntu 23.04"
NAME="Ubuntu"
VERSION_ID="23.04"
VERSION="23.04 (Lunar Lobster)"
System hardware: IBM LinuxONE
Details:
During the installation, I set up and actived a vlan device, after the installation, when I login the OS, the vlan device disappeared, I opened the '/etc/netplan/00-installer-config.yaml', double checked the config file, the vlan1300 is existing, and then when I 'netplan apply' to perform the configuration, an error message shows up,
"[?2004hubuntu at ibm:~$
"sudo netplan apply
"[?2004l
"Cannot call openvswitch: ovsdb-server.service is not running.
And during the boot stage, the systemd-networkd-wait-online.se tart
running message shows a lot in the log, not sure these are related.
"M[K[ [0;31m*[0;1;31m*[0m] Job systemd-networkd-wait-online.se tart running (1min 11s / no limit)
"
"M[K[ [0;31m*[0m] Job systemd-networkd-wait-online.se tart running (1min 12s / no limit)
"
"M[K[ [0;31m*[0;1;31m*[0m] Job systemd-networkd-wait-online.se tart running (1min 12s / no limit)
"
"M[K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] Job systemd-networkd-wait-online.se tart running (1min 13s / no limit)
"
"M[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] Job systemd-networkd-wait-online.se tart running (1min 13s / no limit)
"
"M[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] Job systemd-networkd-wait-online.se tart running (1min 14s / no limit)
"
"M[K[[0;31m*[0;1;31m*[0m[0;31m* [0m] Job systemd-networkd-wait-online.se tart running (1min 14s / no limit)
"
"M[K[[0;1;31m*[0m[0;31m* [0m] Job systemd-networkd-wait-online.se tart running (1min 15s / no limit)
Attached the operating system boot log.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2022030/+subscriptions
More information about the foundations-bugs
mailing list