[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-11-16 Thread Launchpad Bug Tracker
This bug was fixed in the package livecd-rootfs - 2.719.3 --- livecd-rootfs (2.719.3) hirsute; urgency=medium [ Thomas Bechtold ] * magic-proxy: Replace http.client with urllib calls. live-build/auto/build: change iptables calls to query rules and quickly check that

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-11-08 Thread Thomas Bechtold
SRU verification for hirsute: I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.719.3). See - https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/308173 -

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-11-08 Thread Launchpad Bug Tracker
This bug was fixed in the package livecd-rootfs - 2.664.33 --- livecd-rootfs (2.664.33) focal; urgency=medium * Install cloud-initramfs-growroot to actually enable rootfs resize. * Fix a grub error by making sure the unicode.pf2 font is installed in the right path for

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-11-05 Thread Steve Langasek
Hello Dimitri, or anyone else affected, Accepted livecd-rootfs into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.719.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-11-03 Thread Thomas Bechtold
I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.664.33). See - https://launchpadlibrarian.net/566970666/buildlog_ubuntu_focal_amd64_amd64-tarball_proposed_BUILDING.txt.gz - https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/307101

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-10-29 Thread Thomas Bechtold
Bionic is not affected ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title:

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-10-28 Thread Brian Murray
Hello Dimitri, or anyone else affected, Accepted livecd-rootfs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.664.32 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-10-27 Thread Robie Basak
The livecd-rootfs SRU for Bionic, Focal and Hirsute is currently blocked by another SRU in progress. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title:

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Thomas Bechtold
** Changed in: livecd-rootfs (Ubuntu Hirsute) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Thomas Bechtold

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Brian Murray
** Also affects: iptables (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: iptables (Ubuntu

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Thomas Bechtold
** Description changed: - [Why SRU?] + [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-09-28 Thread Thomas Bechtold
** Description changed: + [Why SRU?] + The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-07-30 Thread Brian Murray
** Changed in: lxd (Ubuntu) Status: New => Invalid ** Changed in: iptables (Ubuntu) Status: New => Invalid ** Changed in: launchpad-buildd Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-05-07 Thread Launchpad Bug Tracker
This bug was fixed in the package livecd-rootfs - 2.721 --- livecd-rootfs (2.721) impish; urgency=medium [ Dimitri John Ledkov ] * 999-cpc-fixes: enable more code on grub2 armhf & arm64 (LP: #1925780) * Add support for generic preinstalled images. LP: #1923832 * Change

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-04-14 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~xnox/livecd-rootfs/+git/livecd-rootfs/+merge/401108 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title:

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Dimitri John Ledkov
The nat fiddles are not visible inside the container network namespace. Thus I am wondering if there is an odd interaction between namespace, nftables based iptables vs legacy iptables. I.e. whilst the host is configured using legacy iptables, maybe the lxd guests must be using legacy iptables

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~xnox/livecd-rootfs/+git/livecd-rootfs/+merge/399383 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title:

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Colin Watson
We do some slightly fiddly stuff in launchpad-buildd to set up a bridge - see the `iptables` and `start_bridge` methods in https://git.launchpad.net/launchpad- buildd/tree/lpbuildd/target/lxd.py#n233. Might this be relevant? -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Dimitri John Ledkov
i think either -L or -S "made everything work". Note that there is no iptables installs in the lxd container, and we install iptables on the fly. nftables are not installed either, because that's not in main. So when lxd container started, nothing did "restore" of any default chains I don't

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Colin Watson
** Project changed: launchpad => launchpad-buildd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Alex Murray
Good point re google.com - I just repeated the above test but replacing www.google.com with http://neverssl.com and verified it worked as expected so it doesn't look like http->https redirect affected the results. Hmmm perhaps there is something else at play compared to when testing locally vs on

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Dimitri John Ledkov
However I do not think that google.com is a good test, as it will try to redirect to https, no? and magic proxy only does things with http. We are failing to reach http ftpmaster.internal. I am now trying to rewrite bits of magic-proxy to use more of urllib and surface more HTTP and IO errors.

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-09 Thread Dimitri John Ledkov
@alex Thanks for trying this. And yes, we have been unable to reproduce this outside of launchpad. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title:

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-08 Thread Alex Murray
I tried to reproduce this in an up-to-date bionic VM as follows: # inside the bionic VM sudo snap install lxd sudo lxd init # accept defauls sudo lxc launch ubuntu-daily:hirsute hirsute sudo lxc exec hirsute /bin/bash # then inside the hirsute container install livecd-rootfs apt update apt

[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2

2021-03-05 Thread Dimitri John Ledkov
** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in Launchpad itself: New