yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #81998
[Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN
Some additional information:
Early in the subiquity installation process (right after disk device enablement) I can see two files in /etc/netplan/:
00-installer-config.yaml
50-cloud-init.yaml.dist-subiquity
I think both are not as they should be for this VLAN environment.
After replacing them with:
network:
version: 2
renderer: networkd
ethernets:
encc000:
dhcp4: no
dhcp6: no
vlans:
encc000.2653:
id: 2653
link: encc000
addresses: [ 10.245.236.15/24 ]
gateway4: 10.245.236.1
nameservers:
search: [ canonical.com ]
addresses:
- 10.245.236.1
I was able to bring up the network (in the subiquity shell) using netplan apply.
(I also disabled/enabled 0.0.c000 - but I think it was not needed).
Unfortunately there is still no network online after the post-install reboot:
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul
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,UP,LOWER_UP> mtu 1500 qdisc mq state UP group d
efault qlen 1000
link/ether 16:9e:e9:36:c4:90 brd ff:ff:ff:ff:ff:ff
inet6 fe80::149e:e9ff:fe36:c490/64 scope link
valid_lft forever preferred_lft forever
3: encc000.2653@encc000: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueu
e state UP group default qlen 1000
link/ether 16:9e:e9:36:c4:90 brd ff:ff:ff:ff:ff:ff
inet6 fe80::149e:e9ff:fe36:c490/64 scope link
valid_lft forever preferred_lft forever
...since the following netplan yaml is in place - which is not correct:
$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
encc000: {}
version: 2
vlans:
encc000.2653:
id: 2653
link: encc000
nameservers:
addresses:
- 10.245.236.1
Replacing it again by the above (known to work) yaml allows to bring the
network up again (with the help of netplan).
I add cloud-init as affected package and let the maintainers decide if
this is a duplicate or not (see previous comment).
** Also affects: cloud-init
Importance: Undecided
Status: New
--
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:
New
Status in subiquity:
New
Status in Ubuntu on IBM z Systems:
New
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
