On Fri, Dec 16, 2022 at 03:48:00PM -0800, Ross Vandegrift wrote:
> At a high level the issue is: firewalld.service forces network-pre.target
> after
> sysinit.target, but cloud-init.service forces the other way around. In
> detail,
> using < to represent Before, the imposed orderings look like:
On Mon, Dec 12, 2022 at 05:41:46PM -0800, Noah Meyerhans wrote:
> On 12/12/2022 6:44 AM, Sam Hartman wrote:
> > >> From my quick read: Michael Biebl proposes dropping
> > >> network-pre.target
> > Ross> from cloud-init's After=, and replacing it with each of the
> > Ross> config
On 12/12/2022 6:44 AM, Sam Hartman wrote:
>> From my quick read: Michael Biebl proposes dropping
>> network-pre.target
Ross> from cloud-init's After=, and replacing it with each of the
Ross> config backends that cloud-init supports. This sounds pretty
Ross> reasonable, b
> "Ross" == Ross Vandegrift writes:
>> From my quick read: Michael Biebl proposes dropping
>> network-pre.target
Ross> from cloud-init's After=, and replacing it with each of the
Ross> config backends that cloud-init supports. This sounds pretty
Ross> reasonable, but also
Hi Ross,
> 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.
Is there a way to bypass "Conflicts" and install such packages anyway,
in case the user finds a way to
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
Package: cloud-init
Version: 20.4.1-2+deb11u1
Severity: important
X-Debbugs-Cc: xi...@australdx.fr
Dear Maintainer,
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
7 matches
Mail list logo
