Long network timeout on booting subiquity test ISO
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Fix Released
|
High
|
Dimitri John Ledkov | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
netplan.io (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Similar to: https:/
Again in this case, systemd-
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-
Name Version Rev Developer Notes
subiquity 0.0.38 7 canonical classic
ubuntu-
ii nplan 0.26 amd64 YAML network configuration abstraction for various backends
ubuntu-
ls: cannot access '/etc/networkd': No such file or directory
2 ubuntu-
lo: flags=73<
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-
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: <BROADCAST,
link/ether 52:54:00:ee:14:92 brd ff:ff:ff:ff:ff:ff
ubuntu-
1: lo: <LOOPBACK,
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,
link/ether 52:54:00:ee:14:92 brd ff:ff:ff:ff:ff:ff
ubuntu-
-- 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-
Sep 14 03:25:35 ubuntu-server systemd-
Sep 14 03:27:35 ubuntu-server systemd-
Sep 14 03:27:35 ubuntu-server systemd[1]: systemd-
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-
Sep 14 03:27:35 ubuntu-server systemd[1]: systemd-
ubuntu-
ubuntu-
2min 227ms systemd-
3.532s lxd-containers.
2.513s dev-sr0.device
2.511s dev-loop0.device
1.298s accounts-
ubuntu-
no longer affects: | subiquity |
Changed in subiquity: | |
importance: | Undecided → High |
Changed in nplan (Ubuntu): | |
importance: | Undecided → High |
tags: | added: id-59dd420cf831805e3c59b950 |
affects: | nplan (Ubuntu) → netplan.io (Ubuntu) |
Changed in subiquity: | |
status: | New → Fix Released |
Changed in livecd-rootfs (Ubuntu): | |
status: | Fix Committed → Fix Released |
I think xnox has a plan for this (although the DHCP-by-default thing will also fix it in most situations)