** Changed in: canonical-livepatch-client
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2019997
Title:
pro livepatch status incorrect when run as normal user
To m
This bug was fixed in the package ubuntu-advantage-tools - 31.2~16.04
---
ubuntu-advantage-tools (31.2~16.04) xenial; urgency=medium
* Backport new upstream release (LP: #2048921)
ubuntu-advantage-tools (31.2) noble; urgency=medium
* properly rename logrotate conffile to avoid d
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04
---
ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium
* Backport new upstream release (LP: #2048921)
ubuntu-advantage-tools (31.2) noble; urgency=medium
* properly rename logrotate conffile to avoid d
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04
---
ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium
* Backport new upstream release (LP: #2048921)
ubuntu-advantage-tools (31.2) noble; urgency=medium
* properly rename logrotate conffile to avoid du
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04
---
ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium
* Backport new upstream release (LP: #2048921)
ubuntu-advantage-tools (31.2) noble; urgency=medium
* properly rename logrotate conffile to avoid du
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10
---
ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium
* Backport new upstream release (LP: #2048921)
ubuntu-advantage-tools (31.2) noble; urgency=medium
* properly rename logrotate conffile to avoid d
I've run the test plan for the ubuntu-advantage-tools fix to this bug on
xenial, bionic, focal and jammy. livepatch is not supported on mantic,
so this bug doesn't actually affect mantic. The tests passed and logs
are attached.
The autopkgtest failure on mantic ppc64el looks like a flaky
infrastru
** Description changed:
[ Impact ]
pro status shows livepatch as "disabled" when "canonical-livepatch"
returns an error. This can be misleading. It would be more helpful to
propagate the error message up to the user through pro status; that is
what the fix does.
[ Test Plan ]