eucalyptus upstart job doesn't start NC or CC services
Bug #504521 reported by
Mathias Gug
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eucalyptus (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland | ||
| Lucid |
Fix Released
|
High
|
Dustin Kirkland | ||
Bug Description
On an NC, doing a "start eucalyptus" does not start eucalyptus-nc. However Walrus, SC, Cloud services can all be started with start eucalyptus. The same is true for the CC service. The eucalyptus upstart job could be used to start any of the eucalyptus services.
Revision history for this message
| Dustin Kirkland (kirkland) wrote | #1 |
| Changed in eucalyptus (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Dustin Kirkland (kirkland) wrote | #2 |
Revision history for this message
| Thierry Carrez (ttx) wrote | #3 |
Revision history for this message
| Dustin Kirkland (kirkland) wrote | #4 |
| Changed in eucalyptus (Ubuntu): | |
| importance: | Low → High |
| assignee: | nobody → Dustin Kirkland (kirkland) |
| status: | Triaged → Fix Committed |
| milestone: | none → lucid-alpha-3 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Mathias-
So I have some code (attached) that *should* do this for us. Basically, we need to create a dummy event (a long sleep) in the eucalyptus upstart job if this is a eucalyptus node.
However, I'm having upstart troubles. Using the attached patch, I can:
* eucalyptus & eucalyptus-nc to start on boot
* eucalyptus & eucalyptus-nc to stop on "sudo stop eucalyptus"
But when I try to "sudo start eucalyptus", eucalyptus starts, but not eucalyptus-nc. It has something to do with the "and libvirt-bin". If I drop that off, that works, but that would cause a regression elsewhere.