I just successfully installed and configured an Ubuntu Core 18 image for Intel Dawson Canyon and June Canyon NUC by following this official guide to run (mainly) my Nextcloud instance.
The choice of Ubuntu Core for me is to spend the less time as possible on manual OPS action. And for years it has done a good job (before this install, my server was on a raspi).
After finishing the migration to this new server (physical machine, an intel NUC), I thought it would be cool to enable Livepatch.
I have an Ubuntu account where my Ubuntu member is well activated (50 machines possible, already 1 active only: my desktop), so my Ubuntu Pro dashboard looks like this:
I have installed the canonical-livepatch snap, and tried to attach my server to my account (Note that my ubuntu core machine is already "linked" to my account to add my sudoer user+ssh key, during Ubuntu Core install step, not sure it counts):
$ sudo canonical-livepatch status --verbose
Machine is not enabled. Please run 'sudo canonical-livepatch enable' with the token obtained from https://ubuntu.com/livepatch.
$ sudo canonical-livepatch enable
token not provided
$ sudo canonical-livepatch enable HereIsMyToken
failed to register client: unauthorized
$ sudo canonical-livepatch attach HereIsMyToken
subcommand "attach" unknown
Officials guides mention commands line that are not on Ubuntu Core or just outdated (sudo pro attach TheToken , sudo ua attach TheToken, …), but the manual is explicit about the token after enable. It still fails. Am I doing it wrong?
$ sudo canonical-livepatch enable --help
canonical-livepatch enable - enable livepatching on the machine
USAGE:
canonical-livepatch enable <token>
FLAGS:
--az (= "")
The availability zone of the instance the livepatch client is being enabled on.
--cloud (= "")
The public cloud name this livepatch client is being enabled on.
--region (= "")
The region of the instance the livepatch client is being enabled on.
Here just a little check that my connection is OK (I did installed the snap a moment ago anyway.):
$ ping canonical.com
PING canonical.com(website-content-cache-1.canonical.com (2620:2d:4000:1::26)) 56 data bytes
64 bytes from website-content-cache-1.canonical.com (2620:2d:4000:1::26): icmp_seq=1 ttl=54 time=8.74 ms
64 bytes from website-content-cache-1.canonical.com (2620:2d:4000:1::26): icmp_seq=2 ttl=54 time=8.72 ms
64 bytes from website-content-cache-1.canonical.com (2620:2d:4000:1::26): icmp_seq=3 ttl=54 time=8.68 ms
64 bytes from website-content-cache-1.canonical.com (2620:2d:4000:1::26): icmp_seq=4 ttl=54 time=8.71 ms
64 bytes from website-content-cache-1.canonical.com (2620:2d:4000:1::26): icmp_seq=5 ttl=54 time=8.76 ms
64 bytes from website-content-cache-1.canonical.com (2620:2d:4000:1::26): icmp_seq=6 ttl=54 time=8.73 ms
^C
--- canonical.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5009ms
rtt min/avg/max/mdev = 8.682/8.726/8.761/0.059 ms
