When using today's ISO, with only a single disk drive attached, and snap
refreshed from edge channel, one should be able to complete the install
with networking not getting interrupted, and correctly have networking
in the target too.
** Changed in: ubuntu-z-systems
Status: New => Fix Released
** Changed in: subiquity
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1868246
Title:
No network after subiquity LPAR installation on s390x with VLAN
Status in cloud-init:
Invalid
Status in subiquity:
Fix Released
Status in Ubuntu on IBM z Systems:
Fix Released
Bug description:
I tried today an subiquity LPAR installation using the latest ISO (March 19)
that includes the latest 20.03 subiquity.
The installation itself completed fine, but after the post-install reboot the
system didn't had a network active - please note that the LPAR is connected to
a VLAN.
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
defaul
t 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: encc000: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default q
len 1000
link/ether a2:8d:91:85:12:e3 brd ff:ff:ff:ff:ff:ff
3: enP1p0s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default
qlen 1000
link/ether 82:0c:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff
4: enP1p0s0d1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
defaul
t qlen 1000
link/ether 82:0c:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff
5: enP2p0s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default
qlen 1000
link/ether 82:0c:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff
6: enP2p0s0d1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
defaul
t qlen 1000
link/ether 82:0c:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff
Wanting to have a look at the netplan config it turned out that there is no
yaml file:
$ ls -l /etc/netplan/
total 0
Adding one manually and applying it worked fine.
So looks like the installer does not properly generate or copy a
01-netcfg.yaml to /etc/netplan.
Please see below the entire steps as well as a compressed file with
the entire content of /var/log
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1868246/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
