do-release-upgrade incorrectly reports no upgrade available if it cannot connect to changelogs.ubuntu.com:443

Bug #1856066 reported by Simon Déziel
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

We use apt-cacher-ng configured as apt proxy on every machine and when trying to upgrade a Xenial machine, I got this:

# do-release-upgrade
Checking for a new Ubuntu release
No new release found.

Running tcpdump showed that do-release-upgrade tried to reach changelogs.ubuntu.com:443 with a proxy CONNECT through our apt-cacher-ng. Our apt-cacher-ng returned: "403 CONNECT denied (ask the admin to allow HTTPS tunnels)".

do-release-upgrade should not ignore those errors silently, it should report whatever failure it received.

# lsb_release -rc
Release: 16.04
Codename: xenial

# apt-cache policy ubuntu-release-upgrader-core
ubuntu-release-upgrader-core:
  Installed: 1:16.04.29
  Candidate: 1:16.04.29
  Version table:
 *** 1:16.04.29 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:16.04.25 500
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
     1:16.04.12 500
        500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Tags: xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Changed in ubuntu-release-upgrader (Ubuntu):
status: Confirmed → Triaged
tags: added: xenial
summary: - do-release-upgrade ncorrectly reports no upgrade available if it cannot
+ do-release-upgrade incorrectly reports no upgrade available if it cannot
connect to changelogs.ubuntu.com:443
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.