Control: forwarded -1 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1956629
Hi Guillaume, On Tue, Dec 06, 2022 at 06:26:26PM +0100, Guillaume Knispel wrote: > firewalld and cloud-init have ordering cycles between their systemd unit > files, leading to more or less broken boot results when both are installed > and active, because at each boot systemd decides to skip a > non-deterministically choosen service (not necessarily cloud-init or > firewalld) to break the cycle. Thanks for bringing this to our attention. There's a few useful discussions: https://github.com/firewalld/firewalld/issues/414 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1956629 >From my quick read: Michael Biebl proposes dropping network-pre.target from cloud-init's After=, and replacing it with each of the config backends that cloud-init supports. This sounds pretty reasonable, but also like something that upstream should address first. Should we consider adding "Conflicts: firewalld" to cloud-init before the freeze? That's not optimal of course, but it'd prevent a user from ending up in this situation for now. Thanks, Ross
