This bug was fixed in the package ufw - 0.36.1-3ubuntu1
---
ufw (0.36.1-3ubuntu1) jammy; urgency=medium
* debian/ufw.service: add back DefaultDependencies=no and instead add
Wants/After local-fs.target. This will avoid a dependency on sysinit while
ensuring that filesystems
** Tags removed: block-proposed block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
Title:
ufw 0.36.1-3 introduces ordering cycle, breaking network
https://launchpad.net/ubuntu/+source/ufw/0.36.1-3ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
Title:
ufw 0.36.1-3 introduces ordering cycle, breaking
** Changed in: ufw (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Oh! I missed from the initial report that network-pre was deleted which
clears up things considerably on my end (since I wasn't able to
reproduce, I didn't see it locally either). :)
Preparing an upload now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> cloud-init shouldn't care cause the ufw service doesn't do anything
unless ufw is enabled (and even when it is enabled, it just loads
firewall rules).
It doesn't care about ufw at all, systemd has noticed a cycle between
the units and deleted network-pre.target start job (or cloud-init in
#1),
> This makes me want to understand the cloud-init configuration that is
in play. Can you share it?
I'm thinking I should upload:
DefaultDependencies=no
Before=network-pre.target
Wants=network-pre.target local-fs.target
After=local-fs.target
Do you have any objections? This would remove the
> I don't believe your reproducer is valid - cloud-init is not installed
anymore, as autopkgtest-buildvm-ubuntu-cloud removes it when building
the VM, whereas it remains on the cloud images, as it's needed there to
actually get the IP address during boot.
Note, in
Though arguably I'd expect this to be fixed by removing
DefaultDependencies again, if I looked at this correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
Title:
I have added a cloud-init task, to draw cloud-init people in to help get
this resolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
Title:
ufw 0.36.1-3 introduces
I don't believe your reproducer is valid - cloud-init is not installed
anymore, as autopkgtest-buildvm-ubuntu-cloud removes it when building
the VM, whereas it remains on the cloud images, as it's needed there to
actually get the IP address during boot.
Removing the DefaultDependencies=no means
** Attachment added: "plot-2.svg"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1950039/+attachment/5550320/+files/plot-2.svg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
** Attachment added: "plot-3.svg"
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1950039/+attachment/5550321/+files/plot-3.svg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Attached are two 'systemd-analyze plot's for the autopktest jammy system
with cloud-init and ufw installed. plot-2.svg is for booting the system
with 0.36.1-2 (current jammy) and plot-3.svg is 0.36.1-3 (proposed
jammy). Notice how plot-2.svg, ufw and systemd-networkd start quite a
bit earlier than
@juliank - note I wasn't so much talking about 'blame' as much as
understanding, so I apologize if it came across that way. Since I wasn't
able to reproduce, I was trying to reason through my thoughts to help
the discussion go further since I'm not able to diagnose it myself.
In a nutshell, I
I think we can rebuild images on the staging autopkgtest instance with
the packages from proposed and run a couple hundred tests there and see
if it still breaks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
This broke the autopkgtest cloud. Networking did not came up and hence
no tests passed anymore. We absolutely must not let this pass until we
are sure the problem is resolved, as rebuilding images without it is
hard. (so setting it to incomplete is fairly dangerous).
Debian does not use
** Changed in: ufw (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
Title:
ufw 0.36.1-3 introduces ordering cycle,
@juliank - where did you see these errors? I booted with a freshly
created autopkgtest jammy vm, installed the package from proposed and it
worked fine.
Please see my previous comments-- this does not seem to be a bug in ufw
since it is using the documented unit setup that systemd recommends for
Also, to be clear, when I say I can't look at the ufw portions 'for a
while', I mean ~10 days (doing this from my phone).
Thinking about this, my thinking is this is less about the Before/Wants
on network-pre and the removal of DefaultDependencies and more about
Before=network being removed
I mention firewalld cause while ufw could be reverted, firewalld users
would presumably also hit it, as well as any other software that does
it. If the ufw change is reverted, IME someone should audit the archive
for other occurrences of this pattern and update the units accordingly).
--
You
Fyi, the current configuration is the same as firewalld upstream and
what is in Debian, Moreover it is following systemd documentation for
firewall software so I wonder if the change simply uncovered a latent
bug
Fyi, I won't be able to look at this for a while so if you need to back
it out,
The issue may be the removal of DefaultDependencies=no, but I'm not 100%
sure - it may also be the additional Before/Wants
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
The cycle occurs in other places to, e.g. basic.target <->
sysinit.target
[ 12.918119] systemd[1]: basic.target: Found ordering cycle on
sysinit.target/start
[ 12.919241] systemd[1]: basic.target: Found dependency on
cloud-init.service/start
[ 12.920347] systemd[1]: basic.target: Found
** Tags added: block-proposed
** Tags added: block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1950039
Title:
ufw 0.36.1-3 introduces ordering cycle,
25 matches
Mail list logo
