For the record: the "hang" was the ~ 10s timeout for IPv6 RA. I was
testing with Yakkety/Zesty's QEMU whose "user" net has a builtin RA (you
get an fec0::* address), while xenial's doesn't.

We enable RA (on the client side) by default, and IMHO should really do
so -- selling a new solution in 2016 which does not speak IPv6 would be
hilarious. You can't also significantly reduce the timeout, as this
would make RA unreliable and it's presumably also a specification
somewhere.

So AFAICS the remaining issue is just to make networkd run before
dbus.service/socket in systemd, and add "After=networking.service
systemd-networkd-wait-online.service" and drop
"Wants=networking.service" in cloud-init.service.

** Changed in: systemd (Ubuntu)
    Milestone: None => ubuntu-16.11

** Changed in: systemd (Ubuntu)
       Status: Triaged => In Progress

** Changed in: systemd (Ubuntu Xenial)
       Status: Triaged => In Progress

** Changed in: systemd (Ubuntu Xenial)
     Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636912

Title:
  systemd-networkd runs too late for cloud-init.service (net)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to