Merge ~sergiodj/britney/+git/hints-ubuntu:ubuntu-fan-focal into ~ubuntu-release/britney/+git/hints-ubuntu:focal

Proposed by Sergio Durigan Junior
Status: Needs review
Proposed branch: ~sergiodj/britney/+git/hints-ubuntu:ubuntu-fan-focal
Merge into: ~ubuntu-release/britney/+git/hints-ubuntu:focal
Diff against target: 12 lines (+4/-0)
1 file modified
ubuntu-release (+4/-0)
Reviewer Review Type Date Requested Status
Steve Langasek Disapprove
Review via email: mp+419138@code.launchpad.net

Description of the change

This MP adds a hint for ubuntu-fan/0.12.13 on all architectures.

The package is currently failing and blocking docker.io from migrating. After spending a few hours investigating, here are my conclusions:

- I cannot reproduce the issue locally, even after setting up a container with proxy settings similar to those being used by autopkgtest.u.c. The tests pass all the time, no matter if I use packages from -updates and/or -proposed.

- While testing on autopkgtest.u.c, the "docker" dep8 test always fails. I was able to determine that "docker pull" will fail to pull images from whatever registry you specify, so that's not something related to Dockerhub (initially I was thinking that we could be reaching some rate-limit).

- I also thought it could be something related to not being able to properly setting docker's proxy settings, but as I said above I did try to run the test in a VM with the squid.internal proxy configured and it passed.

- docker.io's dep8 tests are passing OK. I've tested the package locally and it is working.

Having said all that, I'm reasonably convinced that the problem here is not on docker.io, but rather on some weird interaction between ubuntu-fan and autopkgtest.u.c. It *could* still be a problem with proxy settings on docker, but that's not a bug.

To post a comment you must log in.
Revision history for this message
Steve Langasek (vorlon) wrote :

Regressing the autopkgtests of another package in the archive as part of an SRU, even if we think it's a bug in those other tests, is generally not acceptable. To do so for a package in main is doubly bad. If the ubuntu-fan tests are buggy, you need to (work with the ubuntu-fan maintainers to) fix the tests.

review: Disapprove
Revision history for this message
Sergio Durigan Junior (sergiodj) wrote :

Unmerged commits

a43ad8b... by Sergio Durigan Junior

force-badtest ubuntu-fan/0.12.13

ubuntu-fan is acting weird on autopkgtest.u.c, most likely due to some
proxy issue there. I cannot reproduce the problem locally, and it's
currently blocking docker.io from migrating.

Signed-off-by: Sergio Durigan Junior <email address hidden>

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/ubuntu-release b/ubuntu-release
2index 04f9c42..16a357f 100644
3--- a/ubuntu-release
4+++ b/ubuntu-release
5@@ -399,3 +399,7 @@ force-badtest vagrant-libvirt/0.0.45-2/amd64 vagrant-libvirt/0.0.45-2/s390x
6 force-badtest debootstrap/all/s390x
7 # fails only on lxc hosts
8 force-badtest sbuild/all/armhf
9+
10+# ubuntu-fan is failing when running "docker pull" on autopkgtest.u.c,
11+# most likely due to some weird problem with proxy configuration.
12+force-badtest ubuntu-fan/0.12.13

Subscribers

People subscribed via source and target branches