** No longer affects: cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be waiting on
To manage notifications about
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,
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
Bugs, which
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'.
**
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'.
**
** 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
** Branch linked: lp:~ubuntu-branches/ubuntu/saucy/cloud-init/saucy-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be
** 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
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be waiting on
To manage notifications
** 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
** Branch linked: lp:~ubuntu-core-dev/ubuntu/raring/upstart/raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
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
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)
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
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)
** 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
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be waiting on
To manage notifications about this
** 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
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
** Changed in: upstart (Ubuntu Raring)
Assignee: (unassigned) = Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that
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
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
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
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
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
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.
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
** 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
** 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
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.
*
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.
*
** 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:
** 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
** 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:
** 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
** 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
** 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
Bugs, which is subscribed to
** 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
** 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
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
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,
** Branch linked: lp:~jamesodhunt/ubuntu/saucy/upstart/bug-1124384
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be waiting
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
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,
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
** 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
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
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
** 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.
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
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
57 matches
Mail list logo
