[Bug 2049785] Re: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update-manager at 118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loads:decode:raw_decode

Nathan Teodosio 2049785 at bugs.launchpad.net
Fri Mar 1 10:43:59 UTC 2024


I got a Bionic ISO and run it in a virtual machine.

Enabled proposed and now upgrading update-manager forces the
installation of a newer ubuntu-advantage-tools:

--->
$ sudo apt install update-manager --verbose-versions
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
   python3-update-manager (1:18.04.11.23)
   ubuntu-advantage-tools (31.1~18.04)
   ubuntu-pro-client (31.1~18.04)
   ubuntu-pro-client-l10n (31.1~18.04)
   update-manager-core (1:18.04.11.23)
The following NEW packages will be installed:
   ubuntu-pro-client (31.1~18.04)
   ubuntu-pro-client-l10n (31.1~18.04)
The following packages will be upgraded:
   python3-update-manager (1:18.04.11.13 => 1:18.04.11.23)
   ubuntu-advantage-tools (27.2.2~18.04.1 => 31.1~18.04)
   update-manager (1:18.04.11.13 => 1:18.04.11.23)
   update-manager-core (1:18.04.11.13 => 1:18.04.11.23)
4 upgraded, 2 newly installed, 0 to remove and 376 not upgraded.
Need to get 820 kB of archives.
After this operation, 1,570 kB disk space will be freed.
Do you want to continue? [Y/n] 
<---

I confirm then that launching and finishing update-manager without
internet connection produces no error any more.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2049785

Title:
  /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update-
  manager at 118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loads:decode:raw_decode

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in update-manager source package in Bionic:
  Fix Committed
Status in update-manager source package in Focal:
  Fix Committed
Status in update-manager source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  The new Ubuntu Pro integration hits an exception when the pro client
  call isn't returning a value json output

  * Test case

  Check that reports on
  https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea
  stop

  Also on a system not connected to pro, install an old ubuntu-
  advantage-tools 27 (outdated version), disconnect from internet and
  start update-manager, it should list the updates and not error out

  * Regression potential

  The code is changing the callback to get the list of pro updates to
  use the ubuntu-advantage-tools python API instead of calling the
  cmdline client. If there is an issue with the new API the pro updates
  listing on non pro-attached system could be incorrect or the client
  could hit a new exception

  --------------------------------------

  In JournalErrors:

  --->
  Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-91-generic&series=focal
  Cannot verify certificate of server
  Please check your openssl configuration.
  [info] A new version is available: 30~20.04
  Please run:
  sudo apt-get install ubuntu-advantage-tools
  <---

  Is it the ubuntu-advantage-tools version problem, is it the failure to
  access contracts.canonical.com? Should we switch to calling the API
  directly as in 24.04[1] or handle the exception?

  [1] https://code.launchpad.net/~nteodosio/update-manager/+git/update-
  manager/+merge/456088

  ------

  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager.  This problem was most recently seen with package version 1:20.04.10.18, the problem page at https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2049785/+subscriptions




More information about the foundations-bugs mailing list