--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
- From: Thomas Goirand <zigo@debian.org>
- Date: Fri, 19 Jun 2015 00:26:07 +0200
- Message-id: <20150618222607.24506.94089.reportbug@buzig2.mirantis.com>
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian.org@packages.debian.org
Usertags: pu
Dear release team,
In Sid, I added missing systemd .service files to the cloud-init package,
because without them, the ordering when starting cloud-init is completely
wrong. With the default OpenStack image at cdimage.debian.org, you may
not find out about it, until you add some new daemons in the startup
process.
I wish to also update cloud-init in Jessie, to fix this issue, and
add the missing .service files. I have attached the debdiff between Debian
release -2 and -3.
1/ Would you agree with such a change?
2/ What should be the version number for this update? Should I use
0.7.6~bzr976-2+deb8u1 ? Or is 0.7.6~bzr976-3~deb8u1 more appropriate in
this case?
Please let me know,
Cheers,
Thomas Goirand (zigo)
diff -Nru cloud-init-0.7.6~bzr976/debian/changelog cloud-init-0.7.6~bzr976/debian/changelog
--- cloud-init-0.7.6~bzr976/debian/changelog 2014-07-05 11:29:08.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/changelog 2015-06-08 10:04:04.000000000 +0000
@@ -1,3 +1,9 @@
+cloud-init (0.7.6~bzr976-3) unstable; urgency=medium
+
+ * Added upstream .service files (Closes: #784083).
+
+ -- Thomas Goirand <zigo@debian.org> Mon, 08 Jun 2015 10:03:48 +0000
+
cloud-init (0.7.6~bzr976-2) unstable; urgency=medium
* Build-depend on iproute2 instead of iproute (Closes: #753695).
diff -Nru cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-config.service cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-config.service
--- cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-config.service 1970-01-01 00:00:00.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-config.service 2015-06-08 10:02:59.000000000 +0000
@@ -0,0 +1,17 @@
+[Unit]
+Description=Apply the settings specified in cloud-config
+After=network.target syslog.target cloud-config.target
+Requires=cloud-config.target
+Wants=network.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/cloud-init modules --mode=config
+RemainAfterExit=yes
+TimeoutSec=0
+
+# Output needs to appear in instance console output
+StandardOutput=journal+console
+
+[Install]
+WantedBy=multi-user.target
diff -Nru cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-final.service cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-final.service
--- cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-final.service 1970-01-01 00:00:00.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-final.service 2015-06-08 10:02:59.000000000 +0000
@@ -0,0 +1,17 @@
+[Unit]
+Description=Execute cloud user/final scripts
+After=network.target syslog.target cloud-config.service rc-local.service
+Requires=cloud-config.target
+Wants=network.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/cloud-init modules --mode=final
+RemainAfterExit=yes
+TimeoutSec=0
+
+# Output needs to appear in instance console output
+StandardOutput=journal+console
+
+[Install]
+WantedBy=multi-user.target
diff -Nru cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-init-local.service cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-init-local.service
--- cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-init-local.service 1970-01-01 00:00:00.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-init-local.service 2015-06-08 10:03:00.000000000 +0000
@@ -0,0 +1,16 @@
+[Unit]
+Description=Initial cloud-init job (pre-networking)
+Wants=local-fs.target
+After=local-fs.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/cloud-init init --local
+RemainAfterExit=yes
+TimeoutSec=0
+
+# Output needs to appear in instance console output
+StandardOutput=journal+console
+
+[Install]
+WantedBy=multi-user.target
diff -Nru cloud-init-0.7.6~bzr976/debian/cloud-init.service cloud-init-0.7.6~bzr976/debian/cloud-init.service
--- cloud-init-0.7.6~bzr976/debian/cloud-init.service 1970-01-01 00:00:00.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/cloud-init.service 2015-06-08 10:03:00.000000000 +0000
@@ -0,0 +1,18 @@
+[Unit]
+Description=Initial cloud-init job (metadata service crawler)
+After=local-fs.target network.target cloud-init-local.service
+Before=sshd.service sshd-keygen.service
+Requires=network.target
+Wants=local-fs.target cloud-init-local.service sshd.service sshd-keygen.service
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/cloud-init init
+RemainAfterExit=yes
+TimeoutSec=0
+
+# Output needs to appear in instance console output
+StandardOutput=journal+console
+
+[Install]
+WantedBy=multi-user.target
diff -Nru cloud-init-0.7.6~bzr976/debian/control cloud-init-0.7.6~bzr976/debian/control
--- cloud-init-0.7.6~bzr976/debian/control 2014-07-05 11:14:31.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/control 2015-06-08 12:40:18.000000000 +0000
@@ -6,6 +6,7 @@
Section: admin
Priority: optional
Build-Depends: debhelper (>= 9),
+ dh-systemd,
iproute2,
po-debconf,
pyflakes,
diff -Nru cloud-init-0.7.6~bzr976/debian/rules cloud-init-0.7.6~bzr976/debian/rules
--- cloud-init-0.7.6~bzr976/debian/rules 2014-04-12 07:13:31.000000000 +0000
+++ cloud-init-0.7.6~bzr976/debian/rules 2015-06-08 12:40:30.000000000 +0000
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
%:
- dh $@ --with python2 --buildsystem=python_distutils
+ dh $@ --with python2,systemd --buildsystem=python_distutils
override_dh_install:
dh_install
--- End Message ---
--- Begin Message ---
- To: Thomas Goirand <zigo@debian.org>, 789214-done@bugs.debian.org, Julien Cristau <jcristau@debian.org>
- Cc: Charles Plessy <plessy@debian.org>, Martin Zobel-Helas <zobel@debian.org>, Bastian Blank <waldi@debian.org>
- Subject: Re: Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Sun, 17 Jun 2018 20:27:48 +0100
- Message-id: <1529263668.2082.46.camel@adam-barratt.org.uk>
- In-reply-to: <1058373d-009c-8981-9266-88f6dde85da8@debian.org>
- References: <20150619051437.GW2120@betterave.cristau.org> <5583CB63.2060902@debian.org> <20150623204820.GG2120@betterave.cristau.org> <20150819020138.GA20220@aqwa.igloo> <55D71800.7060004__13410.1362586536$1440159892$gmane$org@debian.org> <5622D616.8010304@debian.org> <20151112044950.GA3037@falafel.plessy.net> <5644A00A.90206@debian.org> <20151123123201.GA14915@bubu.igloo> <56532ADD.3010901@debian.org> <20160628091504.GE3361@betterave.cristau.org> <1058373d-009c-8981-9266-88f6dde85da8@debian.org>
Control: tags -1 + wontfix
On Thu, 2016-06-30 at 14:26 +0200, Thomas Goirand wrote:
> On 06/28/2016 11:15 AM, Julien Cristau wrote:
> > I believe I have asked multiple times for a clear explanation of
> > what
> > this bug is, its effect, and why the proposed fix is the right one,
> > and
> > I don't remember seeing a satisfactory answer. If I missed it, I'd
> > appreciate a pointer.
> >
> > Cheers,
> > Julien
>
> Julien,
>
> You missed it indeed. Ben Hutchings replied in debian-devel about it,
> https://lists.debian.org/debian-devel/2015/11/msg00447.html
>
> He wrote:
>
> "systemd doesn't support sysvinit scripts in runlevel S, so it would
> still be necessary to add native systemd units."
>
> You can read the full thread if you want some context.
Unfortunately things seem to have stalled after the above exchange, and
the window for getting fixes in to the final point release for jessie
(before it moves to LTS support) has now closed.
Sorry we weren't able to deal with this update.
Regards,
Adam
--- End Message ---