[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
raring has seen the end of its life and is no longer receiving any updates. Marking the raring task for this ticket as Won't Fix. ** Changed in: cloud-init (Ubuntu Raring) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
Landing this fix in raring was blocked by bug #1199778, which we ran out of time to resolve before the 13.10 release. My work-in-progress branch is available at lp:~vorlon/ubuntu/raring/upstart/lp.1199778 in case anyone else wants to pick this up for 13.04. Otherwise, this bug is 'wontfix'. ** Changed in: upstart (Ubuntu Raring) Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Branch linked: lp:~ubuntu-branches/ubuntu/saucy/cloud-init/saucy- proposed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
this was fixed in cloud-init runk at revno 824. It will be released in 0.7.3 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Branch linked: lp:ubuntu/cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Branch linked: lp:~ubuntu-core-dev/ubuntu/raring/upstart/raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
Bug #1199778 has been identified as a regression in the new version of upstart in saucy. We are assuming this bug also affects the serialization backport that was uploaded to raring-proposed. As a result, this SRU is being marked verification-failed and the current package has been withdrawn from raring-proposed to avoid other users installing it and hitting this bug while it's being resolved. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
This bug was fixed in the package cloud-init - 0.7.3~bzr826-0ubuntu1 --- cloud-init (0.7.3~bzr826-0ubuntu1) saucy; urgency=low * New upstream snapshot. * Fix omnibus support (LP: #1182265) * invoke 'initctl reload-configuration' on upstart jobs again (LP: #1124384) * Remove unowned files in /etc/apt/apt.conf.d/ after purge. (Closes #674237) -- Scott Moser smo...@ubuntu.com Wed, 10 Jul 2013 13:35:59 -0400 ** Changed in: cloud-init (Ubuntu Saucy) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Branch linked: lp:cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Changed in: upstart (Ubuntu Raring) Assignee: (unassigned) = Dmitrijs Ledkovs (xnox) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
Hello Ben, or anyone else affected, Accepted upstart into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/upstart/1.8-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
I confirm the regression in upstart 1.8-0ubuntu1.1 in Raring which also exists in 1.8-0ubuntu7 in Saucy caused by a typo in upstart.postinst: 83 elif dpkg --compare-version $UPSTART_VERSION_RUNNING ge 1.6.1; then The right option is --compare-versions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
Hello Ben, or anyone else affected, Accepted upstart into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/upstart/1.8-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: upstart (Ubuntu Raring) Status: Confirmed = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu Raring) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu Raring) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Description changed: [Impact] - * The status of blocked events was not preserved, when upstart -performed stateful re-execution or configuration reload. Thus jobs -with complex start/stop conditions (one or more and clauses), -with at least one event emitted before re-exec/reload, may not -execute when remaining conditions are finally satisfied. + * The status of blocked events was not preserved, when upstart + performed stateful re-execution or configuration reload. Thus jobs + with complex start/stop conditions (one or more and clauses), + with at least one event emitted before re-exec/reload, may not + execute when remaining conditions are finally satisfied. - * Above may prevent certain system to function correctly, and in the -cases similar to cloud-init instances may even cause failure to -boot. + * Above may prevent certain system to function correctly, and in the + cases similar to cloud-init instances may even cause failure to + boot. - * The fix includes incriminating reference counts on blocked events, -whilst job configuration is reloaded and fully serialising all -upstart objects, including blocked events, during stateful -re-execution. + * The fix includes incriminating reference counts on blocked events, + whilst job configuration is reloaded and fully serialising all + upstart objects, including blocked events, during stateful + re-execution. - * Since previous versions of upstart, do not serialise blocked events -the upgrade needs special casing. On upgrade upstart will perform -stateful re-execution, unless runlevel 2 has been already -reached. Instead upstart, will re-executed at system shutdown. This -should allow upgrading upstart during early boot of cloud-init -instances. But do note, that old instance of upstart will still be -running as init and the running machine will still be affected by -the bug described here. + * Since previous versions of upstart, do not serialise blocked events + the upgrade needs special casing. On upgrade upstart will perform + stateful re-execution, unless runlevel 2 has been already + reached. Instead upstart, will re-executed at system shutdown. This + should allow upgrading upstart during early boot of cloud-init + instances. But do note, that old instance of upstart will still be + running as init and the running machine will still be affected by + the bug described here. [Test Case] - * Create a sample job /etc/init/foo.conf similar to this: + * Create a sample job /etc/init/foo.conf similar to this: start on (event1 and event2) task exec date - * Test reload configuration works correctly: + * Test reload configuration works correctly: $ sudo status foo foo stop/waiting $ sudo initctl emit -n event1 $ sudo initctl reload-configuration $ sudo initctl emit -n event2 $ sudo tail /var/log/upstart/foo.log At the end one should see a timestamp appended in the foo.log. - * Test stateful re-exec works correctly: + * Test stateful re-exec works correctly: $ sudo initctl emit -n event1 $ sudo telinit u $ sudo initctl emit -n event2 $ sudo tail /var/log/upstart/foo.log + * Start an ubuntu-cloud image (in lxc or cloud) with apt-get update + upgrade enabled going from upstart version without this fix included to + a one that does have it. Cloud-final should finish and boot-finished + under /var/lib/cloud/instances/*/boot-finished. Please note this test + should be performed in isolation from dbus security update that does + partial stateful re-exec at the moment. + [Regression Potential] - * The bug fix introduced here is fairly large (approx 1.5k line diff) -but comes with comprehensive set of test-suites to verify the two -bug fixes as well as all possible combinations of stateful -re-execution serialisation formats. Majority of code changes are -for additional [de]serialisation, which follow existing well tested -code pattern. And changes to reference counting have been carefully -reviewed and tested by multiple developers. + * The bug fix introduced here is fairly large (approx 1.5k line diff) + but comes with comprehensive set of test-suites to verify the two + bug fixes as well as all possible combinations of stateful + re-execution serialisation formats. Majority of code changes are + for additional [de]serialisation, which follow existing well tested + code pattern. And changes to reference counting have been carefully + reviewed and tested by multiple developers. - * While the bug report indicates a severe problem, it was not noticed -until recently, as the system must be under heavy race conditions -to become affected by this bug. Since systems reaching stable state, -with little or no blocked events left, would not normally be -affected. + * While the bug report indicates a severe
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
upstart (1.8-0ubuntu4) saucy; urgency=low [ James Hunt ] * Cherry pick lp:~jamesodhunt/upstart/serialise-remaining-objects (LP:#1124384): - Preserve event blockers during configuration reload. - Serialise deserialise blocking events during stateful re-execution. * debian/manpages/upstart-events.7: Added ':sys:restarted'. * debian/upstart.postinst: Don't re-exec if runlevel is not 2 yet (to allow cloud-init to dist-upgrade upstart safeily in early boot). [ Dmitrijs Ledkovs ] * Upload to saucy. * Use serial-tests harness during build, instead of the automake's 1.13 default parallel-tests harness. * Enable parallel build by default. -- Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Thu, 06 Jun 2013 16:15:09 +0100 ** Changed in: upstart (Ubuntu Saucy) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Also affects: upstart (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: upstart (Ubuntu Saucy) Importance: Medium Assignee: James Hunt (jamesodhunt) Status: Confirmed ** Also affects: cloud-init (Ubuntu Saucy) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Description changed: + [Impact] + + * The status of blocked events was not preserved, when upstart +performed stateful re-execution or configuration reload. Thus jobs +with complex start/stop conditions (one or more and clauses), +with at least one event emitted before re-exec/reload, may not +execute when remaining conditions are finally satisfied. + + * Above may prevent certain system to function correctly, and in the +cases similar to cloud-init instances may even cause failure to +boot. + + * The fix includes incriminating reference counts on blocked events, +whilst job configuration is reloaded and fully serialising all +upstart objects, including blocked events, during stateful +re-execution. + + * Since previous versions of upstart, do not serialise blocked events +the upgrade needs special casing. On upgrade upstart will perform +stateful re-execution, unless runlevel 2 has been already +reached. Instead upstart, will re-executed at system shutdown. This +should allow upgrading upstart during early boot of cloud-init +instances. But do note, that old instance of upstart will still be +running as init and the running machine will still be affected by +the bug described here. + + [Test Case] + + * Create a sample job /etc/init/foo.conf similar to this: + + start on (event1 and event2) + task + exec date + + * Test reload configuration works correctly: + + $ sudo status foo + foo stop/waiting + $ sudo initctl emit -n event1 + $ sudo initctl reload-configuration + $ sudo initctl emit -n event2 + $ sudo tail /var/log/upstart/foo.log + + At the end one should see a timestamp appended in the foo.log. + + * Test stateful re-exec works correctly: + + $ sudo initctl emit -n event1 + $ sudo telinit u + $ sudo initctl emit -n event2 + $ sudo tail /var/log/upstart/foo.log + + [Regression Potential] + + * The bug fix introduced here is fairly large (approx 1.5k line diff) +but comes with comprehensive set of test-suites to verify the two +bug fixes as well as all possible combinations of stateful +re-execution serialisation formats. Majority of code changes are +for additional [de]serialisation, which follow existing well tested +code pattern. And changes to reference counting have been carefully +reviewed and tested by multiple developers. + + * While the bug report indicates a severe problem, it was not noticed +until recently, as the system must be under heavy race conditions +to become affected by this bug. Since systems reaching stable state, +with little or no blocked events left, would not normally be +affected. + + * Overall regression potential is deemed low. + + [Original Bug Report] + Under bug 1080841 we made cloud-init invoke 'initctl reload- configuration' after it wrote a upstart job. This was necessary because inotify is not supported on all filesystems (overlayfs being the one of most current interst). This seems to be causing upstart some pain, and resulting in cloud-final (and 'rc') not being run. Easy user-data to reproduce the problem is: #cloud-config-archive - content: | #cloud-boothook #!/bin/sh touch /run/cloud-init-upstart-reload # hack, see trunk commit 783 - content: | #!/bin/sh echo $(date -R): user-script run === | tee /run/user-script.log - content: | #upstart-job description a test upstart job start on stopped rc RUNLEVEL=[2345] console output task script echo $(date -R): upstart job run === | tee /run/upstart-job.log end script You should (and do on quantal) end up with 2 files written to /run. I've verified that the same behavior is true on quantal. If you change cloud-init to notify upstart about a job immediately after it writes it, then quantal's upstart gets confused also. Related bugs: * bug 1080841: should reload configuration if an upstart job is added * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Also affects: cloud-init Importance: Undecided Status: New ** Changed in: cloud-init Status: New = Confirmed ** Changed in: cloud-init Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Branch linked: lp:~jamesodhunt/ubuntu/saucy/upstart/bug-1124384 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Branch linked: lp:~xnox/ubuntu/saucy/upstart/fix-reload-upgrade-bug -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
ppa:xnox/backports has the updated upstart package that has the following fixes: * reload configuration always works and all events are preserved * the postinst script was modified to not execute stateful re-exec if runlevel 2 has not been reached yet The reason for the latter, is that we still loose events that are blocking jobs that are not running yet across the stateful re-exec, because EventJobOperators (aka start_on stop_on conditions) are not serialised to include progress information w.r.t. their states (e.g. TRUE or FALSE for each condition to tell apart if it has fired or not yet). The above fixes allow to always run reload-configuration, including early boot. And safeguard against automatic re-execution if upstart package is upgraded during early boot. To fix stateful re-execution in early boot, we need to serialise all objects used by upstart which upstream has avoided to do so far. Also it's questionable if stateful re-execution in early boot is a desired requirement. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
On Wed, May 01, 2013 at 12:11:19AM -, Dmitrijs Ledkovs wrote: To fix stateful re-execution in early boot, we need to serialise all objects used by upstart which upstream has avoided to do so far. Also it's questionable if stateful re-execution in early boot is a desired requirement. No, it isn't. cloud-init needs to be able to run a dist-upgrade of arbitrary packages, including upstart and core libraries, prior to starting services in a cloud instance. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
The attached is a minimal fix for the problem that applies to lp:upstart. I've tested this in Scotts LXC test scenario with reload-configuration being called mid-boot and the system boots correctly. We still need to finish writing the tests for this fix - that work will have to be completed at the sprint next week. ** Patch added: upstart-bug-1124384-minimal-fix.diff https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3654975/+files/upstart-bug-1124384-minimal-fix.diff ** Changed in: upstart (Ubuntu) Assignee: (unassigned) = James Hunt (jamesodhunt) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
** Summary changed: - reload-configuration can confuse upstart + Configuration reload clears event that others jobs may be waiting on -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: Configuration reload clears event that others jobs may be waiting on
So we've spent a good part of the afternoon going through the two cloud- init bugs with James and came to the conclusion that they are actually the same bug. Both initctl --reload-configuration and an upstart stateful re-exec cause upstart to reload its configuration, destroy existing jobclass entries and create new ones. As part of the process of destroy and re-creating job class entries, upstart decrements the reference counter of some related objects, including emitted events. That has the result that if a job depends on two events, one that has already been emitted and another that hasn't been emitted yet and that the job that emitted the first event is being reloaded, then the record of that event will be dropped, leading to a failure to start the job (as only half the start condition will match). The part of the code that causes this issue is post-reexec, which means that once we come up with a fix for this, we'll be able to SRU it and have upstart re-exec itself, applying the fix in the process. That also means that we can't SRU any of upstart's dependencies until this issue is resolved. James is currently working on testcases for the various scenarios that we know we need to support, so we can have comprehensive regression tests before we attempt to sort this issue. Our current hope is to have a fix for this by the end of the week. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: Configuration reload clears event that others jobs may be waiting on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
