Maybe systemd on ppc64el too? 1974s Reading package lists... 1974s E: The repository 'http://ports.ubuntu.com plucky InRelease' is not signed. 1974s E: Failed to fetch http://ports.ubuntu.com/dists/plucky/InRelease 403 Forbidden [IP: 10.151.41.7 3128] 1974s E: Failed to fetch http://ports.ubuntu.com/dists/plucky-updates/InRelease 403 Forbidden [IP: 10.151.41.7 3128] 1974s E: The repository 'http://ports.ubuntu.com plucky-updates InRelease' is not signed. 1974s E: Failed to fetch http://ports.ubuntu.com/dists/plucky-security/InRelease 403 Forbidden [IP: 10.151.41.7 3128] 1974s E: The repository 'http://ports.ubuntu.com plucky-security InRelease' is not signed. 1974s ‣ "apt-get -o APT::Architecture=ppc64el -o APT::Architectures=ppc64el -o APT::Install-Recommends=false -o APT::Immediate-Configure=off -o APT::Get::Assume-Yes=true -o APT::Get::AutomaticRemove=true -o APT::Get::Allow-Change-Held-Packages=true -o APT::Get::Allow-Remove-Essential=true -o APT::Sandbox::User=root -o Acquire::AllowReleaseInfoChange=true -o Acquire::Check-Valid-Until=false -o Dir::Cache=/var/cache/apt -o Dir::State=/var/lib/apt -o Dir::Log=/var/log/apt -o Dir::State::Status=/buildroot/var/lib/dpkg/status -o Dir::Bin::DPkg=/usr/bin/dpkg -o Debug::NoLocking=true -o DPkg::Options::=--root=/buildroot -o DPkg::Options::=--force-unsafe-io -o DPkg::Options::=--force-architecture -o DPkg::Options::=--force-depends -o DPkg::Options::=--no-debsig -o DPkg::Use-Pty=false -o DPkg::Install::Recursive::Minimum=1000 -o pkgCacheGen::ForceEssential=, -o Acquire::http::Proxy=http://egress.ps7.internal:3128/ -o Acquire::https::Proxy=http://egress.ps7.internal:3128/ update" returned non-zero exit code 100. 1974s FAILED: .
Last success I can see in https://autopkgtest.ubuntu.com/packages/systemd/plucky/ppc64el was on bos03, so PS6. https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- plucky/plucky/amd64/s/systemd/20250722_142127_0e92d@/log.gz ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - autopkgtests fail on PS7 due to mandatory proxy + autopkgtests fail on PS7 due to missing proxy rules -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport 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 systemd package in Ubuntu: New Status in ubuntu-boot-test package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: New Status in update-manager package in Ubuntu: Triaged 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
