Ubuntu
cloud-init package

  1. Bug #1870346
  2. Comment #8

Comment 8 for bug 1870346

Revision history for this message
Dan Watkins (oddbloke) wrote :

Looking at the journal, I see that systemd-networkd does know about wlan0, and reports Link UP for it when cloud-init would expect system networking to be configured:

  Mar 18 19:32:59.099186 ubuntu systemd-networkd[1121]: wlan0: Link UP

is before:

  Mar 18 19:32:59.107823 ubuntu systemd[1]: Finished Wait for Network to be Configured.

but we also see:

  Mar 18 19:32:59.129316 ubuntu systemd-networkd[1121]: eth0: Link UP

when I don't believe we're expecting any link on eth0 (though maybe I'm mistaken about the configuration of this particular device), so the wlan0 line may be a red herring.

I do see later in the journal:

  Mar 18 19:33:08.385332 ubuntu systemd[1]: Starting WPA supplicant...

which is well after cloud-init would expect networking to be up. Is it possible that systemd-networkd-wait-online.service doesn't know how to handle waiting for wifi correctly? (Or is this just a symptom of not having the renderer: set? I'm a little out of my depth here.)