snappy.autopilot service fails to start when no network connection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
~# systemctl status snappy-
● snappy-
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Thu 2015-10-29 13:00:00 UTC; 30min ago
Process: 2631 ExecStart=
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:/
Oct 29 13:00:00 odroid systemd[1]: snappy-
Oct 29 13:00:00 odroid systemd[1]: Unit snappy-
Oct 29 13:00:00 odroid systemd[1]: snappy-
That service should be error resilient and should not fail when boot happens without a network connection.
Behavior is seen on
ubuntu-core 196 (15.04/edge)