*** This bug is a duplicate of bug 1655458 ***
https://bugs.launchpad.net/bugs/1655458
Thanks for this bug.
A bit of information that would be helpful would be getting the
machine-id from canonical-livepatch status --verbose (*not* the
sensitive machine-token) or cat /etc/machine-id.
We are seeing issues with multiple machines hitting the same endpoint
with duplicated machine-id uuid. In some cases we've seen cloud
providers generating non-unique machine-ids on their images.
In these cases, the machine who livepatch enabled most recently is the
only one authorized to use the registered livepatch all other machines
get a 403 error. I'll see if we can dig up more details on this for your
specific machine-ids though. Will continue this conversation on #1655458
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642581
Title:
Livepatch checkState: check-failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1642581/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
