[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#805866: marked as done (Broken LSB headers (cloud-init-local service should start before networking service))

Your message dated Sat, 22 Jul 2017 21:32:34 +0200
with message-id <39829237-7ac8-440e-58ce-457035bbe8d7@debian.org>
and subject line This bug can be closed
has caused the Debian Bug report #805866,
regarding Broken LSB headers (cloud-init-local service should start before networking service)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
805866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805866
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cloud-init
Version: 0.7.6~bzr976-2
Severity: normal

Dear Maintainer,

cloud-init doesn't provide systemd startup files but only the sysv one.

So when systemd-sysv creates the compatibility startup files for
systemd, cloud-init-local.service depends of 'sysinit.target',
that depends of 'networking.service'.
(see the outpout of systemctl list-dependencies below).

But the service 'cloud-init-local' must start before networking.
That service is designed to configure network stuffs and some other
stuffs. And ensures that no dhcp/autoconfiguration are done to avoid 
any (tiny) security issue.

Backporting systemd startup files from upstream should fix the issue.
I'm unsure we can fix it without that.

Cheers,
Mehdi Abaakouk

# systemctl list-dependencies  cloud-init-local.service 
cloud-init-local.service
● ├─system.slice
● └─basic.target
●   ├─paths.target
●   ├─slices.target
●   │ ├─-.slice
●   │ └─system.slice
●   ├─sockets.target
●   │ ├─systemd-initctl.socket
●   │ ├─systemd-journald-dev-log.socket
●   │ ├─systemd-journald.socket
●   │ ├─systemd-shutdownd.socket
●   │ ├─systemd-udevd-control.socket
●   │ └─systemd-udevd-kernel.socket
●   ├─sysinit.target
●   │ ├─debian-fixup.service
●   │ ├─dev-hugepages.mount
●   │ ├─dev-mqueue.mount
●   │ ├─kbd.service
●   │ ├─kmod-static-nodes.service
●   │ ├─networking.service
●   │ ├─proc-sys-fs-binfmt_misc.automount
●   │ ├─sys-fs-fuse-connections.mount
●   │ ├─sys-kernel-config.mount
●   │ ├─sys-kernel-debug.mount
●   │ ├─systemd-ask-password-console.path
●   │ ├─systemd-binfmt.service
●   │ ├─systemd-journal-flush.service
●   │ ├─systemd-journald.service
●   │ ├─systemd-modules-load.service
●   │ ├─systemd-random-seed.service
●   │ ├─systemd-sysctl.service
●   │ ├─systemd-tmpfiles-setup-dev.service
●   │ ├─systemd-tmpfiles-setup.service
●   │ ├─systemd-udev-trigger.service
●   │ ├─systemd-udevd.service
●   │ ├─systemd-update-utmp.service
●   │ ├─udev-finish.service
●   │ ├─cryptsetup.target
●   │ ├─local-fs.target
●   │ │ ├─-.mount
●   │ │ ├─systemd-fsck-root.service
●   │ │ └─systemd-remount-fs.service
●   │ └─swap.target
●   └─timers.target
●     └─systemd-tmpfiles-clean.timer

--- End Message ---
--- Begin Message --- 
Hi,

This bug was related to systemd, which was fixed, but couldn't be
backported to stable. Wheezy is now old-old-stable, I believe we don't
need to care about this anymore, as the issue was solved for Jessie and
Stretch. Therefore, I'm closing the bug.

This here, is a clear failure from the release team to find enough time
to understand this bug. It's disappointing, but such it is...

Cheers,

Thomas Goirand (zigo)

--- End Message ---
Reply to: