Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
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. Cheers, Thomas Goirand (zigo)
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
Control: tag -1 moreinfo On Mon, Nov 23, 2015 at 16:03:57 +0100, Thomas Goirand wrote: > On 11/23/2015 01:32 PM, Charles Plessy wrote: > >>> Le Sun, Oct 18, 2015 at 01:13:26AM +0200, Thomas Goirand a écrit : > > Ping? Is there anyone from the stable release team that could spend a > bit of time here? > > > >> On 11/12/2015 05:49 AM, Charles Plessy wrote: > >>> > >>> I propose that we declare time bankrupcy on that issue, give up on fixing > >>> it, > >>> and update Sid's package instead, which is now seriously outdated. > > > > Le Thu, Nov 12, 2015 at 03:19:54PM +0100, Thomas Goirand a écrit : > >> > >> I was also thinking about it, and though that we can't wait for more. > >> Many people are waiting for this update, including those from Azure. > >> Let's hope the release team accepts the fix anyway at some point. > > > > Hi everybody, > > > > this request for update is stalled, therefore I close it. > > > > Have a nice day, > > No, don't close it. It is a grave bug which I would like to fix. That > the release team don't care enough to investigate in time, or don't > understand the issue at all, isn't a reason good enough to close this > bug. If the release team needs more info, then I will do my best to > provide it, especially that we all do understand they are very busy with > complicated transitions. > > Keeping this bug open doesn't mean w should stop our work in Sid. That, > I agree, we can't delay it, it's been too long already. > 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
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
On 11/23/2015 01:32 PM, Charles Plessy wrote: >>> Le Sun, Oct 18, 2015 at 01:13:26AM +0200, Thomas Goirand a écrit : Ping? Is there anyone from the stable release team that could spend a bit of time here? > >> On 11/12/2015 05:49 AM, Charles Plessy wrote: >>> >>> I propose that we declare time bankrupcy on that issue, give up on fixing >>> it, >>> and update Sid's package instead, which is now seriously outdated. > > Le Thu, Nov 12, 2015 at 03:19:54PM +0100, Thomas Goirand a écrit : >> >> I was also thinking about it, and though that we can't wait for more. >> Many people are waiting for this update, including those from Azure. >> Let's hope the release team accepts the fix anyway at some point. > > Hi everybody, > > this request for update is stalled, therefore I close it. > > Have a nice day, No, don't close it. It is a grave bug which I would like to fix. That the release team don't care enough to investigate in time, or don't understand the issue at all, isn't a reason good enough to close this bug. If the release team needs more info, then I will do my best to provide it, especially that we all do understand they are very busy with complicated transitions. Keeping this bug open doesn't mean w should stop our work in Sid. That, I agree, we can't delay it, it's been too long already. Thomas
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
Le Thu, Nov 12, 2015 at 03:19:54PM +0100, Thomas Goirand a écrit : > > Charles, do you have time to do the update of cloud-init in Sid? Not this week, but maybe the next. Cheers, -- Charles
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
On 11/12/2015 05:49 AM, Charles Plessy wrote: > Le Sun, Oct 18, 2015 at 01:13:26AM +0200, Thomas Goirand a écrit : >> >> Ping? Is there anyone from the stable release team that could spend a >> bit of time here? > > Hello everybody, > > I propose that we declare time bankrupcy on that issue, give up on fixing it, > and update Sid's package instead, which is now seriously outdated. > > Regarless of this bug, there will be the demand for a backport of the version > in Squeeze, which will satisfy Jessie users almost as well as a stable update. > > Have a nice day, Charles, I was also thinking about it, and though that we can't wait for more. Many people are waiting for this update, including those from Azure. Let's hope the release team accepts the fix anyway at some point. Charles, do you have time to do the update of cloud-init in Sid? Cheers, Thomas Goirand (zigo)
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
Le Sun, Oct 18, 2015 at 01:13:26AM +0200, Thomas Goirand a écrit : > > Ping? Is there anyone from the stable release team that could spend a > bit of time here? Hello everybody, I propose that we declare time bankrupcy on that issue, give up on fixing it, and update Sid's package instead, which is now seriously outdated. Regarless of this bug, there will be the demand for a backport of the version in Squeeze, which will satisfy Jessie users almost as well as a stable update. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 -> -3
On 08/21/2015 02:22 PM, Thomas Goirand wrote: > On 08/19/2015 04:01 AM, Charles Plessy wrote: >> Hi Julien and Thomas, >> >> in May, Mehdi Abaakouk wrote in #784083: >> >> After further investigation, the whole cloud-init dependencies chains is >> completely broken with systemd. >> [...] >> This issue is more critical, that I have thought initially, because with >> systemd, the cloud-init behavior is completely unpredictable... >> >> Also, the current packaged debian version source contains the systemd >> unit files, but the binary package doesn't install them. >> >> Then Thomas added the unit files, which fixed the problem. >> >> Then in July, Mehdi Abaakouk confirmed this #784083: >> >> "Note, that I have tested on jessie, the packages that zigo have uploaded >> in sid (0.7.6~bzr976-4) and it works as expected." >> >> Can we go ahead with the proposed stable update ? >> >> Have a nice day, >> >> Charles > > Charles, Julien, > > Julien told me he will review this issue again next week, so let's wait > that. After it's done, the team behind Azure images urgently needs an > update to the latest version of cloud-init in Sid. Julien, is it ok if > we upgrade Sid to the latest upstream, or will it affect the upload to > Stable? > > Cheers, > > Thomas Goirand (zigo) Ping? Is there anyone from the stable release team that could spend a bit of time here? This has a direct influence on the cloud image which we are releasing on each point release, and it is IMO a bad image for Debian if we can't fix this problem. Also, the proposed solution (as a reminder, it is: add a few .service files, because systemd doesn't handle sysv-rc script boot dependencies in a manner which would work with the rest of the boot chain) is IMO very reasonable. Cheers, Thomas Goirand (zigo)
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
On 08/19/2015 04:01 AM, Charles Plessy wrote: Hi Julien and Thomas, in May, Mehdi Abaakouk wrote in #784083: After further investigation, the whole cloud-init dependencies chains is completely broken with systemd. [...] This issue is more critical, that I have thought initially, because with systemd, the cloud-init behavior is completely unpredictable... Also, the current packaged debian version source contains the systemd unit files, but the binary package doesn't install them. Then Thomas added the unit files, which fixed the problem. Then in July, Mehdi Abaakouk confirmed this #784083: Note, that I have tested on jessie, the packages that zigo have uploaded in sid (0.7.6~bzr976-4) and it works as expected. Can we go ahead with the proposed stable update ? Have a nice day, Charles Charles, Julien, Julien told me he will review this issue again next week, so let's wait that. After it's done, the team behind Azure images urgently needs an update to the latest version of cloud-init in Sid. Julien, is it ok if we upgrade Sid to the latest upstream, or will it affect the upload to Stable? Cheers, Thomas Goirand (zigo)
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
Hi Julien and Thomas, in May, Mehdi Abaakouk wrote in #784083: After further investigation, the whole cloud-init dependencies chains is completely broken with systemd. [...] This issue is more critical, that I have thought initially, because with systemd, the cloud-init behavior is completely unpredictable... Also, the current packaged debian version source contains the systemd unit files, but the binary package doesn't install them. Then Thomas added the unit files, which fixed the problem. Then in July, Mehdi Abaakouk confirmed this #784083: Note, that I have tested on jessie, the packages that zigo have uploaded in sid (0.7.6~bzr976-4) and it works as expected. Can we go ahead with the proposed stable update ? Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
On Fri, Jun 19, 2015 at 09:57:23 +0200, Thomas Goirand wrote: Also, I wanted to highlight that the issue isn't about the init scripts, but about the compat mode of systemd which doesn't work. So there's nothing that can be fixed in the init scripts, unfortunately. Assertions like the above aren't very convincing, sorry. Please describe the issue better; I can't see a good description of the issue and justification of the proposed fix either in this bug or in #784083. Cheers, Julien signature.asc Description: Digital signature
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
On 06/19/2015 07:14 AM, Julien Cristau wrote: On Fri, Jun 19, 2015 at 00:26:07 +0200, Thomas Goirand wrote: 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? FWIW, I wouldn't. If the init scripts are broken, fix the init scripts, don't work around them being broken with a more intrusive change. Thanks, Julien Also, I wanted to highlight that the issue isn't about the init scripts, but about the compat mode of systemd which doesn't work. So there's nothing that can be fixed in the init scripts, unfortunately. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
On 06/19/2015 07:14 AM, Julien Cristau wrote: On Fri, Jun 19, 2015 at 00:26:07 +0200, Thomas Goirand wrote: 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? FWIW, I wouldn't. If the init scripts are broken, fix the init scripts, don't work around them being broken with a more intrusive change. Thanks, Julien How do you propose to fix the change when running with systemd then? (the issue doesn't appear if using sysv-rc...) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
On Fri, Jun 19, 2015 at 00:26:07 +0200, Thomas Goirand wrote: 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? FWIW, I wouldn't. If the init scripts are broken, fix the init scripts, don't work around them being broken with a more intrusive change. Thanks, Julien signature.asc Description: Digital signature
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@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.0 + +++ cloud-init-0.7.6~bzr976/debian/changelog 2015-06-08 10:04:04.0 + @@ -1,3 +1,9 @@ +cloud-init (0.7.6~bzr976-3) unstable; urgency=medium + + * Added upstream .service files (Closes: #784083). + + -- Thomas Goirand z...@debian.org Mon, 08 Jun 2015 10:03:48 + + 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.0 + +++ cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-config.service 2015-06-08 10:02:59.0 + @@ -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.0 + +++ cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-final.service 2015-06-08 10:02:59.0 + @@ -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.0 + +++ cloud-init-0.7.6~bzr976/debian/cloud-init.cloud-init-local.service 2015-06-08 10:03:00.0 + @@ -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.0 + +++ cloud-init-0.7.6~bzr976/debian/cloud-init.service 2015-06-08 10:03:00.0 + @@ -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.0 + +++ cloud-init-0.7.6~bzr976/debian/control 2015-06-08 12:40:18.0 + @@ -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
Bug#789214: jessie-pu: package cloud-init/0.7.6~bzr976-2 - -3
Am 19.06.2015 um 00:26 schrieb Thomas Goirand: Package: release.debian.org Severity: normal Tags: jessie User: release.debian@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? All those services have use DefaultDependencies=yes (which is the default), so an explicit Wants=local-fs.target After=local-fs.target is not needed. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
