group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #44696
[Bug 2004650] Re: pro status --all fails on 22.10
This bug was fixed in the package ubuntu-advantage-tools -
27.13.5~22.10.1
---------------
ubuntu-advantage-tools (27.13.5~22.10.1) kinetic; urgency=medium
* Backport new upstream release
ubuntu-advantage-tools (27.13.5~23.04.1) lunar; urgency=medium
* d/ubuntu-advantage-tools.postinst:
- fix version for cleaning the esm-apps stale unauthenticated files
(LP: #2006765)
ubuntu-advantage-tools (27.13.4~23.04.1) lunar; urgency=medium
* d/ubuntu-advantage-tools.postinst:
- remove stale esm-apps unauthenticated caches (LP: #2004193)
* apt-hook:
- Change esm-apps advertisement message on apt upgrade to
make it clearer that the service is providing more upgrades
and not restricting user to only get updates if esm-apps
is enabled (LP: #2006510)
* contract:
- make code aware that the effective date is not a required field
in the machine-token.json file (LP: #2006351)
* esm_cache
- do not fail if we cannot extract information from
/etc/os-release file (LP: #2006508)
* security-status:
- consider packages without a candidate as 'unknown' (LP: #2006049)
* status:
- treat null effective contract dates as unknown/expired
(LP: #2004650)
* timer:
- recycle invalid jobs-status.json file if we detect it is
corrupted (LP: #2006261)
-- Renan Rodrigo <renanrodrigo@xxxxxxxxxxxxx> Thu, 09 Feb 2023
14:36:17 -0300
** Changed in: ubuntu-advantage-tools (Ubuntu Kinetic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2004650
Title:
pro status --all fails on 22.10
Status in ubuntu-advantage-tools package in Ubuntu:
In Progress
Status in ubuntu-advantage-tools source package in Xenial:
Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
Fix Released
Status in ubuntu-advantage-tools source package in Focal:
Fix Released
Status in ubuntu-advantage-tools source package in Jammy:
Fix Released
Status in ubuntu-advantage-tools source package in Kinetic:
Fix Released
Status in ubuntu-advantage-tools source package in Lunar:
In Progress
Bug description:
[ Original Description ]
When running "pro status --all" on kinetic I get an unexpected error.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: ubuntu-advantage-tools 27.13.3~22.10.1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 3 08:13:17 2023
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
InstallationDate: Installed on 2020-05-18 (990 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20200511-12:31
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: Upgraded to kinetic on 2022-08-30 (156 days ago)
cloud-id.txt-error: Invalid command specified 'cloud-id'.
livepatch-status.txt-error: Failed running command '/snap/bin/canonical-livepatch status' [exit(1)]. Message: error executing status: livepatchd error: The platform Ubuntu 22.10 is not supported. exiting.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-05-11T08:18:53
ua-status.json-error: Failed running command 'pro status --format json' [exit(1)]. Message:
[Impact]
If the user has a null effective date in machine-token.json, the pro
status command will fail, since we output that date and we assume that
it should not be null
[ Test Case ]
We provide an integration test result where we modify the contract to
have a null effective date and show that pro status does not break
because of that.
[ Regression potential ]
We are just better handling null effective date on the contract server
response for status. Since we are just addressing a broken scenario,
we don't believe this fix pose a major regression potential
[ Discussion]
If we detect that we have a null effect date delivered on machine-
token.json, we are now showing that date as "Unknown/Expired" on the
pro status output. This will better reflect the situation the machine
is at and while also preventing the command to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2004650/+subscriptions