Autoregistration is always attempted, whatever the post-start scripts return
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Low
|
Thierry Carrez | ||
Karmic |
Fix Released
|
Low
|
Thierry Carrez |
Bug Description
20091006 CD install, eucalyptus 1.6~bzr912-0ubuntu1
Autoregistration works, however strange lines appear in /var/log/syslog:
init: eucalyptus-cc post-start process (959) terminated with status 1
init: eucalyptus-cloud post-start process (896) terminated with status 1
init: eucalyptus-sc post-start process (897) terminated with status 1
init: eucalyptus-walrus post-start process (898) terminated with status 1
Instrumenting the jobs, here is what happens on a eucalyptus start:
eucalyptus-sc poststart begin
eucalyptus-cloud poststart begin
eucalyptus-walrus poststart begin
[sc, cloud and walrus loop several times waiting for the test to succeed]
eucalyptus-cc poststart begin
[cc poststart exits 1 immediately]
[after 27 tries, eucalyptus-cloud poststart exits with 0, success!]
eucalyptus-
eucalyptus-
[sc and walrus poststart still loop, then after 60 tries:]
eucalyptus-walrus poststart exit 1
eucalyptus-
eucalyptus-sc poststart exit 1
eucalyptus-sc-reg begin
eucalyptus-sc-reg end [successful sc registration]
eucalyptus-
Several issues here:
* eucalyptus-
* eucalyptus-cc has a typo that makes it always return 1 immediately (| grep on a separate line)
* The post-start test in eucalyptus-
Related branches
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Medium |
Changed in eucalyptus (Ubuntu Karmic): | |
status: | Triaged → In Progress |
Changed in eucalyptus (Ubuntu Karmic): | |
status: | In Progress → Fix Committed |
Changed in eucalyptus (Ubuntu Karmic): | |
status: | Fix Committed → Fix Released |
To solve issue #1, we can use "stop" without arguments in post-start instead of (or in addition to) exit 1. $IP_ADDR: 8773/services/ Heartbeat doesn't return anything (while I can run instances alright)
Issue #2 is trivial
To solve issue #3 we need a working way to tell that the sc and walrus have been started.
In my testing http://