| 2024-10-16 06:32:09 |
Pushkar Kulkarni |
description |
[ Impact ]
* The merge proposal related [1] fixed the autopkgtest failures, but only for local testing. For the dep8 testing on autopkgtest.ubuntu.com, the tests continue to fail due to 403 errors [2] due to interference of a proxy. This blocks the migration of puppetdb on noble and oracular.
[ Test Plan ]
* Requesting autopkgtests on autopkgtest.ubuntu.com for noble and oracular reveals the failures [2].
[ Where problems could occur ]
Currently, both tests under debian/test fail on oracular and noble [2].
The failures may be locally reproduced by enabling the squid proxy.For example, I used an internal proxy to reproduce the reported failures locally:
autopkgtest puppetdb \
--env='http_proxy=http://<redacted-url>:<redacted-port-number>' \
--apt-pocket=proposed=src:puppetdb -U \
-- lxd autopkgtest/ubuntu/noble/amd64
[1] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516
[2] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516/comments/6 |
[ Impact ]
* The merge proposal related [1] fixed the autopkgtest failures, but only for local testing. For the dep8 testing on autopkgtest.ubuntu.com, the tests continue to fail due to 403 errors [2] due to interference of a proxy. This blocks the migration of puppetdb on noble and oracular.
[ Test Plan ]
* Requesting autopkgtests on autopkgtest.ubuntu.com for noble and oracular reveals the failures [2].
[ Where problems could occur ]
* Currently, both tests under debian/test fail on oracular and noble [2].
The failures may be locally reproduced by enabling the squid proxy.For example, I used an internal proxy to reproduce the reported failures locally:
autopkgtest puppetdb \
--env='http_proxy=http://<redacted-url>:<redacted-port-number>' \
--apt-pocket=proposed=src:puppetdb -U \
-- lxd autopkgtest/ubuntu/noble/amd64
[1] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516
[2] https://bugs.launchpad.net/ubuntu/+source/puppetdb/+bug/2072516/comments/6 |
|
