[Bug 2116119] Re: autopkgtests fail on PS7 due to missing proxy rules
Nick Rosbrook
2116119 at bugs.launchpad.net
Wed Dec 3 13:21:14 UTC 2025
Adding sbuild to the list:
411s Install dose3 build dependencies (apt-based resolver)
411s -----------------------------------------------------
411s
411s Installing build dependencies
411s Reading package lists...
411s Building dependency tree...
411s The following additional packages will be installed:
411s dose-distcheck xz-utils
411s The following NEW packages will be installed:
411s dose-distcheck sbuild-build-depends-dose3-dummy xz-utils
411s 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
411s Need to get 1489 kB of archives.
411s After this operation, 5221 kB of additional disk space will be used.
411s Get:1 copy:/<<RESOLVERDIR>>/apt_archive ./ sbuild-build-depends-dose3-dummy 0.invalid.0 [640 B]
441s Ign:2 http://ftpmaster.internal/ubuntu noble/universe amd64 dose-distcheck amd64 7.0.0-4build3
442s Ign:2 http://ftpmaster.internal/ubuntu noble/universe amd64 dose-distcheck amd64 7.0.0-4build3
443s Ign:3 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
444s Ign:3 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
444s Ign:2 http://ftpmaster.internal/ubuntu noble/universe amd64 dose-distcheck amd64 7.0.0-4build3
446s Ign:3 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
448s Err:2 http://ftpmaster.internal/ubuntu noble/universe amd64 dose-distcheck amd64 7.0.0-4build3
448s Could not connect to ftpmaster.internal:80 (10.131.215.228), connection timed out
450s Ign:3 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
481s Ign:3 http://security.ubuntu.com/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
481s Ign:3 http://ftpmaster.internal/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
481s Err:3 http://ftpmaster.internal/ubuntu noble-updates/main amd64 xz-utils amd64 5.6.1+really5.4.5-1ubuntu0.2
481s Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.83), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.92.23), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out
481s Fetched 640 B in 1min 11s (9 B/s)
481s E: Failed to fetch http://ftpmaster.internal/ubuntu/pool/main/x/xz-utils/xz-utils_5.6.1%2breally5.4.5-1ubuntu0.2_amd64.deb Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Could not connect to archive.ubuntu.com:80 (185.125.190.82), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.83), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.82), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.92.23), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.83), connection timed out Could not connect to archive.ubuntu.com:80 (185.125.190.81), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.91.81), connection timed out
481s E: Failed to fetch http://ftpmaster.internal/ubuntu/pool/universe/d/dose3/dose-distcheck_7.0.0-4build3_amd64.deb Could not connect to ftpmaster.internal:80 (10.131.215.228), connection timed out
481s E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
481s apt-get failed.
481s E: Package installation failed
481s Not removing build depends: cloned chroot in use
482s E: Failed to explain bd-uninstallable
482s
482s +------------------------------------------------------------------------------+
482s | Summary Wed, 03 Dec 2025 09:30:48 +0000 |
482s +------------------------------------------------------------------------------+
482s
482s Build Architecture: amd64
482s Build Type: full
482s Build-Space: n/a
482s Build-Time: 0
482s Distribution: unstable
482s Fail-Stage: explain-bd-uninstallable
482s Host Architecture: amd64
482s Install-Time: 0
482s Job: /tmp/autopkgtest.QaQkFS/autopkgtest_tmp/test-pkg_1.0.dsc
482s Machine Architecture: amd64
482s Package: test-pkg
482s Package-Time: 0
482s Source-Version: 1.0
482s Space: n/a
482s Status: given-back
482s Version: 1.0
482s --------------------------------------------------------------------------------
482s Finished at 2025-12-03T09:28:18Z
482s Build needed 00:00:00, no disk space
482s E: Failed to explain bd-uninstallable
482s autopkgtest [09:30:48]: test unshare: -----------------------]
483s unshare FAIL non-zero exit status 1
483s autopkgtest [09:30:49]: test unshare: - - - - - - - - - - results - - - - - - - - - -
483s autopkgtest [09:30:49]: @@@@@@@@@@@@@@@@@@@@ summary
483s build-procenv FAIL stderr: W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/resolute/InRelease Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::103). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::102). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4000:1::101). - connect (101: Network is unreachable) Cannot initiate the connection to archive.ubuntu.com:80 (2620:2d:4002:1::103). - connect (101: Network is unreachable)
483s unshare FAIL non-zero exit status 1
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/s/sbuild/20251203_093107_b3abe@/log.gz
** Also affects: sbuild (Ubuntu)
Importance: Undecided
Status: New
--
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 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 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