autopkgtest schroot fails with network access
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopkgtest (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned | ||
debootstrap (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
on armhf, the schroot test was skipped previously, because it fails to create the tarball.
222s autopkgtest [16:35:34]: test schroot: [------
224s mknod: /var/lib/
224s E: Cannot install into target '/var/lib/
224s E: Error running debootstrap at /usr/bin/
224s SKIP: Unable to create chroot testing-
224s autopkgtest [16:35:36]: test schroot: -------
227s schroot SKIP exit status 77 and marked as skippable
now, with debootstrap/
385s autopkgtest [09:09:35]: test schroot: [------
685s I: Base system installed successfully.
...
688s I: Please add any additional APT sources to /var/lib/
688s I: schroot chroot configuration written to /etc/schroot/
688s I: Please rename and modify this file as required.
688s mkdir /etc/sbuild/chroot
However the tests fail to recognize the http proxy, so it fails with
757s Err:1 http://
757s Cannot initiate the connection to deb.debian.org:80 (2a04:4e42:
Changed in debootstrap (Ubuntu): | |
status: | New → Invalid |
Changed in autopkgtest (Ubuntu): | |
status: | New → Fix Committed |
Currently the failure in autopkgtest prevents debootstrap migration. But this is not debootstrap fault. So can we ignore the failure and force debootstrap to migrate?