euca_conf --register-nodes should not return 0 if keys cannot be synced
Bug #531195 reported by
Thierry Carrez
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eucalyptus (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland | ||
| Lucid |
Fix Released
|
High
|
Dustin Kirkland | ||
Bug Description
Even if the key synchronization fails, euca_conf --register-nodes returns 0. This results in giving false information to the autoregistration process and making the situation difficult to debug.
This is due to the way the support for multiple IPs is coded: it will not fail (and return nonzero) on the first IP that fails but print out an error message, continue to try adding all the others, and always return 0 at the end. See around line 1437 for details.
| Changed in eucalyptus (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Dustin Kirkland (kirkland) wrote | #1 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| importance: | Medium → High |
Revision history for this message
| Mathias Gug (mathiaz) wrote | #2 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| status: | Triaged → In Progress |
| assignee: | nobody → Dustin Kirkland (kirkland) |
| Changed in eucalyptus (Ubuntu Lucid): | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in eucalyptus (Ubuntu Lucid): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm going to raise this priority to High. I've hit this several times, and it costs me quite a bit of time debugging before I realize that in fact the node registration did not succeed.