[Bug 2116119] Re: autopkgtests fail on PS7 due to missing proxy rules

Myles Penner 2116119 at bugs.launchpad.net
Tue Jan 13 17:39:14 UTC 2026


I added crash to the list as I am seeing the error with a software-
properties SRU regression[1]

 66s Setting up software-properties-common (0.99.49.4) ...
 66s Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
 67s autopkgtest [02:13:00]: test live: [-----------------------
 67s Adding linux-image debug symbols.
 67s Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
 67s Executing: /tmp/apt-key-gpghome.clAl9FGmhp/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys C8CAB6595FDFF622
 97s gpg: keyserver receive failed: Connection timed out
 97s autopkgtest [02:13:30]: test live: -----------------------]
 98s live                 FAIL non-zero exit status 2
 98s autopkgtest [02:13:31]: test live:  - - - - - - - - - - results - - - - - - - - - -
 98s autopkgtest [02:13:31]: @@@@@@@@@@@@@@@@@@@@ summary
 98s live                 FAIL non-zero exit status 2

[1] https://autopkgtest.ubuntu.com/packages/c/crash/noble/amd64

-- 
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/2116119

Title:
  autopkgtests fail on PS7 due to missing proxy rules

Status in ansible-core package in Ubuntu:
  New
Status in apport package in Ubuntu:
  Confirmed
Status in crash package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Triaged
Status in nbd package in Ubuntu:
  Fix Released
Status in sbuild package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-boot-test package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Triaged
Status in ansible-core source package in Noble:
  New
Status in apport source package in Noble:
  New
Status in crash source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  New
Status in nbd source package in Noble:
  New
Status in sbuild source package in Noble:
  New
Status in systemd source package in Noble:
  New
Status in ubuntu-boot-test source package in Noble:
  New
Status in ubuntu-release-upgrader source package in Noble:
  New
Status in update-manager source package in Noble:
  New

Bug description:
  Canonical PS7 (prodstack 7) now requires[1] a proxy for any outgoing
  connection, even to archive.ubuntu.com. This breaks assumptions made
  by some of the update-manager tests[2], which expect a direct
  connection.

  Affected packages (known so far):
  * Apport
  * livecd-rootfs
  * update-manager
  * ubuntu-release-upgrader
  * ubuntu-boot-test
  * ansible-core (See https://github.com/ansible/ansible/issues/77304)

  Long thread on internal mattermost here[3].

  For example:
  1320s ERROR: testOriginMatcherSimple (test_update_origin.TestOriginMatcher.testOriginMatcherSimple)
  1320s ----------------------------------------------------------------------
  1320s Traceback (most recent call last):
  1320s   File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in update
  1320s     res = self._cache.update(fetch_progress, slist, pulse_interval)
  1320s apt_pkg.Error: E:Failed to fetch http://archive.ubuntu.com/ubuntu/dists/noble/InRelease  Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable)

  Curiously, these tests seem to have passed in non-amd64 architectures,
  but closer inspection showed that these ran in good-old-PS6 (bos03),
  where direct connections to archive.ubuntu.com (and
  changelogs.ubuntu.com) are allowed.

  This bug might be invalid for update-manager in the end, and we could
  decide to allow such direct connections in PS7, but for the meantime,
  we need a place to discuss, and reference, because we are about to
  have to skip these tests for SRUs and migrations that this is
  blocking.

  Keep in mind that forcing all these tests to go through a proxy will
  also probably mean we will lose test coverage, since we are losing the
  directly-connected test scenario.

  Some troubleshooting was done already, here is some info.

  a) provisioning of proxy settings for PS7 autopkgtest vms:

    - echo http_proxy=http://egress.ps7.internal:3128/ >> /etc/environment
    - echo https_proxy=http://egress.ps7.internal:3128/ >> /etc/environment
    - echo no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain >> /etc/environment
    - echo 'Acquire::http::Proxy \"http://egress.ps7.internal:3128/\";' > /etc/apt/apt.conf.d/99proxy

  1. No clue where this decision was made
  2. https://autopkgtest.ubuntu.com/results/autopkgtest-questing/questing/amd64/u/update-manager/20250707_093622_8d0d0@/log.gz
  3. https://chat.canonical.com/canonical/pl/g7hugd5p53nwmmibntd359z3gr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible-core/+bug/2116119/+subscriptions




More information about the foundations-bugs mailing list