eucalyptus-nc-publication keeps on respawning when shutting down NC
Bug #534271 reported by
Thierry Carrez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Low
|
Dustin Kirkland |
Bug Description
When shutting down an NC, the shutdown is delayed by multiple eucalyptus-
The job should probably be "stopped on" switching to runlevel 0,1 to avoid that issue.
I suspect the same issue is plaguing all publication jobs that use respawn.
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Low |
Changed in eucalyptus (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Dustin Kirkland (kirkland) |
Changed in eucalyptus (Ubuntu): | |
status: | Triaged → In Progress |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu11
---------------
eucalyptus (1.6.2-0ubuntu11) lucid; urgency=low
* Cherry-pick merge from upstream 1.6.2, now on revision 1207 eucalyptus- nc.dirs, debian/ eucalyptus- nc.postinst: LP: #519653 cc.eucalyptus- cc-publication. upstart, nc.eucalyptus- nc-publication. upstart, sc.eucalyptus- sc-publication. upstart, walrus. eucalyptus- walrus- publication. upstart: LP: #534271
- LP: #532938: fix restarting the cloud controller while instances
are pending, which was causing incorrect address allocation state
* debian/
- ensure that the instance directories are created and owned by
eucalyptus
* eucalyptus-
eucalyptus-
eucalyptus-
eucalyptus-
- stop publication jobs on run-level [!2345], fixes issue where
publication respawning delays shutdown
-- Dustin Kirkland <email address hidden> Mon, 08 Mar 2010 14:23:53 -0600