snappy.autopilot service fails to start when no network connection

[Simon Eisenmann]

~# systemctl status snappy-autopilot.service -l
● snappy-autopilot.service - Ubuntu Core Snappy Autopilot
   Loaded: loaded (/lib/systemd/system/snappy-autopilot.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2015-10-29 13:00:00 UTC; 30min ago
  Process: 2631 ExecStart=/usr/bin/snappy update --automatic-reboot (code=exited, status=1/FAILURE)
 Main PID: 2631 (code=exited, status=1/FAILURE)

Oct 29 13:00:00 odroid systemd[1]: Started Ubuntu Core Snappy Autopilot.
Oct 29 13:00:00 odroid systemd[1]: Starting Ubuntu Core Snappy Autopilot...
Oct 29 13:00:00 odroid snappy[2631]: Get https://system-image.ubuntu.com//ubuntu-core/15.04/edge/generic_armhf/index.json: dial tcp: lookup system-image.ubuntu.com: Temporary failure in name resolution
Oct 29 13:00:00 odroid systemd[1]: snappy-autopilot.service: main process exited, code=exited, status=1/FAILURE
Oct 29 13:00:00 odroid systemd[1]: Unit snappy-autopilot.service entered failed state.
Oct 29 13:00:00 odroid systemd[1]: snappy-autopilot.service failed.

That service should be error resilient and should not fail when boot happens without a network connection.

[Simon Eisenmann (longsleep)]

Behavior is seen on
ubuntu-core 196 (15.04/edge)

[Leo Arias (elopio)]

This is no longer happening in the latest rolling edge.

When I boot my rpi2 without the network cable the service appears as loaded inactive. It doesn't show the FAILURE you pasted in the bug.

Then when I connect the cable, after a while it will run and finish with SUCCESS.

I'm going to mark this as fixed, but if you are still experiencing the problem please let us know.

Thanks!