Can't enable livepatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-advantage-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu 22.04.4 LTS
Release: 22.04
hinkPad-
N: Impossible de trouver le paquet pkgname
I wanted to try ubuntu pro and followed the documentation and after this command:
sudo pro attach *******************
I have noticed that livepatch was disabled and wasn't supposed to
I have tryed a couple of commands:
ThinkPad-
One moment, checking your subscription first
Unexpected error(s) occurred.
For more details, see the log: /var/log/
To file a bug run: ubuntu-bug ubuntu-
ThinkPad-
This machine is already attached to '******
To use a different subscription first run: sudo pro detach.
ThinkPad-
One moment, checking your subscription first
Unable to enable Livepatch: Failed running command '/snap/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 5.15.0-101-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 20 21:08:09 2024
InstallationDate: Installed on 2024-02-19 (30 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
PackageArchitec
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-
UpgradeStatus: Upgraded to jammy on 2024-03-18 (2 days ago)
apparmor_logs.txt: mars 20 21:01:41 julien-
cloud-id.txt-error: Invalid command specified 'cloud-id'.
livepatch-
Failed running command '/snap/
token obtained from https:/
uaclient.conf:
contract_url: https:/
log_level: debug
Hello, Julien
Thanks for reporting this bug
Unfortunately this happened due to an outage in contracts. canonical. com. The service is now back online and everything should be working fine.
Would you mind trying again please?
For the future, we will improve this error message so users know what is happening instead of seeing 'unexpected error'.
As we received many bug reports about this, I am marking this one a duplicate (for easier tracking). Feel free to come back if the error persists though.