** Changed in: netplan
Status: Fix Committed => Fix Released
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchp
Another insight: The t/local/referer.t file of this package fiddles with
the HTTP_PROXY environment variable, which sounds very related, e.g.:
$ grep -Hni HTTP_PROXY t/local/referer.t
t/local/referer.t:20:delete $ENV{HTTP_PROXY};
--
You received this bug notification because you are a memb
This sounds like the squid.internal proxy might be non-
functional/-reachable in lcy02 (and inside armhf/LXD runners) but
working properly in bos03?
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
Matching subs
Remember that the package version that's currently in the archive
carries a delta to disable the affected test.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu.
Matching subscriptions: ubuntu-qa-bugs
https://bug
This is already showing up in component-mismatches, we have MIR ACK and
no security review needed.
Let's move it to the next stage and get it promoted. Please remember to
add a team bug-subscriber, before promotion.
** Changed in: retry (Ubuntu)
Status: In Progress => Fix Committed
--
Yo
Additional fixes pending in
https://github.com/canonical/netplan/pull/510
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2073997
Title:
netplan: routing autopkgtest fails on a
** Changed in: retry (Ubuntu)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2076381
Title:
[MIR] retry
Status in retry pa
Looks like the "modprobe" condition does not fully work in containers,
as it'll try loading the module from within the container, but the
modules will be installed/loaded on the host.
Maybe we should rather check /proc/modules instead.
--
You received this bug notification because you are a memb
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2073997
Title:
netplan: routing autopkgtest fails on armhf
Status in Auto Package Testing:
Fix Released
Status in Netplan:
F
This is apparently related to Ubuntu's apparmor confinement of the LXC
process. Running containers unconfined seems to help:
```
sudo apparmor_parser -R /etc/apparmor.d/usr.bin.lxc-start
sudo ln -s /etc/apparmor.d/usr.bin.lxc-start /etc/apparmor.d/disable/
echo "lxc.apparmor.profile = unconfined"
** Tags added: fr-2551
** Also affects: ubuntu-release-upgrader (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags removed: rls-jj-incoming
--
You received this bug notificatio
11 matches
Mail list logo
