[Bug 1717152] Re: Long network timeout on booting subiquity test ISO
Michael Hudson-Doyle
mwhudsonlp at fastmail.fm
Fri Sep 15 04:24:57 UTC 2017
I think xnox has a plan for this (although the DHCP-by-default thing
will also fix it in most situations)
** Package changed: subiquity (Ubuntu) => subiquity
** Changed in: subiquity
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nplan in Ubuntu.
https://bugs.launchpad.net/bugs/1717152
Title:
Long network timeout on booting subiquity test ISO
Status in subiquity:
New
Status in nplan package in Ubuntu:
New
Bug description:
Similar to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1716500, I get a
long boot timeout on a VM on first boot (no networking has or should
have been brought up, subiquity does that only after a couple of
steps).
Again in this case, systemd-networkd-wait-online.service is on the top
of systemd-analyze blame with ~2m until it times out.
I'm capturing this in case this is a subtly different bug that should
be explored.
Here is relevant debugging interaction, please ask for more if needed,
I can repeat this every time the VM boots.
------------------------------
ubuntu-server at ubuntu-server:~$ snap list subiquity
Name Version Rev Developer Notes
subiquity 0.0.38 7 canonical classic
ubuntu-server at ubuntu-server:~$ dpkg -l |grep nplan
ii nplan 0.26 amd64 YAML network configuration abstraction for various backends
ubuntu-server at ubuntu-server:~⟫ ll /etc/networkd
ls: cannot access '/etc/networkd': No such file or directory
2 ubuntu-server at ubuntu-server:~⟫ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 976 bytes 60864 (60.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 976 bytes 60864 (60.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ubuntu-server at ubuntu-server:~⟫ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:ee:14:92 brd ff:ff:ff:ff:ff:ff
ubuntu-server at ubuntu-server:~⟫ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 52:54:00:ee:14:92 brd ff:ff:ff:ff:ff:ff
ubuntu-server at ubuntu-server:~⟫ journalctl -u systemd-networkd-wait-online.service
-- Logs begin at Thu 2017-09-14 03:25:34 UTC, end at Thu 2017-09-14 03:27:42 UTC. --
Sep 14 03:25:35 ubuntu-server systemd[1]: Starting Wait for Network to be Configured...
Sep 14 03:25:35 ubuntu-server systemd-networkd-wait-online[973]: ignoring: lo
Sep 14 03:25:35 ubuntu-server systemd-networkd-wait-online[973]: ignoring: lo
Sep 14 03:27:35 ubuntu-server systemd-networkd-wait-online[973]: Event loop failed: Connection timed out
Sep 14 03:27:35 ubuntu-server systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILU
Sep 14 03:27:35 ubuntu-server systemd[1]: Failed to start Wait for Network to be Configured.
Sep 14 03:27:35 ubuntu-server systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
Sep 14 03:27:35 ubuntu-server systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
ubuntu-server at ubuntu-server:~⟫
ubuntu-server at ubuntu-server:~⟫ systemd-analyze blame | head -5
2min 227ms systemd-networkd-wait-online.service
3.532s lxd-containers.service
2.513s dev-sr0.device
2.511s dev-loop0.device
1.298s accounts-daemon.service
ubuntu-server at ubuntu-server:~⟫
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1717152/+subscriptions
More information about the foundations-bugs
mailing list