Livepatch service not starting up on 16.04.02

[Srdan Dukic]

I'm trying to install/configure the Canonical Livepatch service on one of my servers, however whenever I try to run the livepatch service, I get the following error from the service startup logs:

Code:

snap[3949]: 2017/02/23 21:57:52 Only Ubuntu 16.04 LTS is supported, exiting.

My problem is that the server is running version 16.04.02:

Code:

root@ip-10-0-16-09:~# cat /etc/issue
Ubuntu 16.04.2 LTS

root@ip-10-0-16-09:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial

root@ip-10-0-16-09:~# uname -a
Linux ip-10-0-16-09 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ip-10-0-16-09:~$ apt-cache policy snap
snap:
  Installed: (none)
  Candidate: 2013-11-29-1ubuntu2.16.04.1
  Version table:
     2013-11-29-1ubuntu2.16.04.1 500
        500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
     2013-11-29-1ubuntu2 500
        500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

Is this limitation on purpose? It seems to me that a minor version upgrade should be supported as well, or is this not the case?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: snap (not installed)
ProcVersionSignature: User Name 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri Feb 24 03:32:40 2017
Ec2AMI: ami-c135f3aa
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1e
Ec2InstanceType: t2.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: snap
UpgradeStatus: Upgraded to xenial on 2017-01-17 (38 days ago)

[Srdan Dukic (srdan-dukic)]

So, to update this bug report the SystemD init system periodically tried to start up the "snap.canonical-livepatch.canonical-livepatchd.service" and at some point around Feb 24th, 21:53 UTC time, it started working:
Code:

Feb 24 03:03:56 ip-10-0-16-09 /usr/bin/snap[5967]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 24 03:03:56 ip-10-0-16-09 snap[5967]: 2017/02/24 03:03:56 Only Ubuntu 16.04 LTS is supported, exiting.
Feb 24 03:03:56 ip-10-0-16-09 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Main process exited, code=exited, status=1/FAILURE
Feb 24 03:03:56 ip-10-0-16-09 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Unit entered failed state.
Feb 24 03:03:56 ip-10-0-16-09 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Failed with result 'exit-code'.
Feb 24 03:03:57 ip-10-0-16-09 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Service hold-off time over, scheduling restart.
Feb 24 03:03:57 ip-10-0-16-09 systemd[1]: Stopped Service for snap application canonical-livepatch.canonical-livepatchd.
Feb 24 03:03:57 ip-10-0-16-09 systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Start request repeated too quickly.
Feb 24 03:03:57 ip-10-0-16-09 systemd[1]: Failed to start Service for snap application canonical-livepatch.canonical-livepatchd.
Feb 24 21:53:50 ip-10-0-16-09 systemd[1]: Stopped Service for snap application canonical-livepatch.canonical-livepatchd.
Feb 24 21:53:51 ip-10-0-16-09 systemd[1]: Started Service for snap application canonical-livepatch.canonical-livepatchd.
Feb 24 21:53:51 ip-10-0-16-09 /usr/bin/snap[13457]: cmd.go:111: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
Feb 24 21:53:52 ip-10-0-16-09 snap[13457]: 2017/02/24 21:53:52 open /var/snap/canonical-livepatch/common/config: no such file or directory
Feb 24 21:53:52 ip-10-0-16-09 canonical-livepatch[13457]: Starting client version 7.21
Feb 24 21:53:52 ip-10-0-16-09 canonical-livepatch[13457]: No machine-token. Please run 'canonical-livepatch enable'!
Feb 24 21:53:52 ip-10-0-16-09 canonical-livepatch[13457]: No payload available.

I have NFI what caused it to start working, neither the apt history or "snap changes" show anything being updated around that time:
Code:

root@ip-10-0-16-09:~# snap changes
ID Status Spawn Ready Summary
10 Done 2017-02-26T03:03:49Z 2017-02-26T03:03:49Z Refresh all snaps: no updates
11 Done 2017-02-26T06:14:13Z 2017-02-26T06:14:13Z Refresh all snaps: no updates
12 Done 2017-02-26T13:01:39Z 2017-02-26T13:01:39Z Refresh all snaps: no updates
13 Done 2017-02-26T19:58:29Z 2017-02-26T19:58:29Z Refresh all snaps: no updates
14 Done 2017-02-27T00:53:39Z 2017-02-27T00:53:39Z Refresh all snaps: no updates

Once the service was running, I was able to validate the key using the "canonical-livepatch enable ...." command and everything is working as expected.

It's still a bit of a mystery as to what caused it to start working. Maybe something changed server side on the Ubuntu Livepatch servers? Maybe there was some kind of "cached" OS version value that needed t...

[Launchpad Janitor (janitor)]

[Expired for snap (Ubuntu) because there has been no activity for 60 days.]