[Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation
Launchpad Bug Tracker
1821867 at bugs.launchpad.net
Mon May 20 08:42:25 UTC 2019
This bug was fixed in the package netplan.io - 0.97-0ubuntu1~18.10.1
---------------
netplan.io (0.97-0ubuntu1~18.10.1) cosmic; urgency=medium
* Backport netplan.io 0.97 to 18.10. (LP: #1828299)
* Keep debian/patches/glib_changes.patch: Make sure tests work on older GLib.
netplan.io (0.97-0ubuntu1) eoan; urgency=medium
* New upstream release: 0.97
- networkd: force bringing up devices with no IP addresses (LP: #1763608)
- Reworked renderer choosing to avoid regression in default renderer when
multiple files specify it globally (LP: #1825206)
- Fixed networkd activation. (LP: #1821867)
* Drop all patches; they are included in the upstream release.
-- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com> Thu, 09 May 2019
11:29:56 -0400
** Changed in: netplan.io (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1821867
Title:
network interface is down after post-install reboot of a default disco
installation
Status in Ubuntu on IBM z Systems:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Status in netplan.io source package in Disco:
Fix Released
Bug description:
[Impact]
Minimal installs using netplan to configure the network.
[Test case]
1) Install Ubuntu minimal server / cloud image
2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
3) Run 'sudo netplan apply'. Verify that the network comes up correctly.
4) Reboot.
5) Verify that the network comes up properly.
[Regression potential]
Minimal; this reverts changes in a package that was never released to -updates, only available as SRU in -proposed and on the devel release. This only changes the systemd config to ensure systemd-networkd.service is included as an active service whenever multi-user.target is wanted (which is the default) instead of only when network-online.target is wanted, since the latter is optional and on some installations is not required at all. This does not change the ordering of boot at all since in both cases systemd-networkd.service is correctly Before=network.target, and it is Before/After, not Wants/Requires, that determines ordering.
---
After doing a default disco installation on s390x using the beta ISO image aka daily from March 26th and the post-install reboot the system restarts aka reipls (in z/VM in this case) but the interface is not brought up.
Hence no remote connections are possible.
The ip cmd shows:
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: enc600: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default ql
en 1000
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
The netplan yaml file looks fine:
cat /etc/netplan/*.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enc600:
addresses: ¬ 10.245.236.27/24 |
gateway4: 10.245.236.1
nameservers:
search: ¬ canonical.com |
addresses:
- "10.245.236.1"
Using ip to bring the interface up doesn't help:
buntu§hwe0007:ß$ sudo ip link set enc600 up
sudo ip link set enc600 up
ubuntu§hwe0007:ß$ ip addr show enc600
ip addr show enc600
2: enc600: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP gr
oup default qlen 1000
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
inet6 fe80::28:bff:fe00:15/64 scope link
valid_lft forever preferred_lft forever
ubuntu§hwe0007:ß$
But finally executing netplan apply does help:
sudo netplan apply --dryrun
sudo netplan apply --dryrun
ubuntu§hwe0007:ß$ sudo netplan apply
sudo netplan apply
ubuntu§hwe0007:ß$ ip addr show enc600
ip addr show enc600
2: enc600: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP gr
oup default qlen 1000
link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff
inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600
valid_lft forever preferred_lft forever
inet6 fe80::28:bff:fe00:15/64 scope link
valid_lft forever preferred_lft forever
ubuntu§hwe0007:ß$
(Sorry for the partly duplicate lines and some strange characters, but
this is due to the fact that I copied the output from the console that
requires a 3270 terminal emulation)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions
More information about the foundations-bugs
mailing list