whirr can have a non-zero return code and unterminated (orphaned) host instances
--------------------------------------------------------------------------------
Key: WHIRR-414
URL: https://issues.apache.org/jira/browse/WHIRR-414
Project: Whirr
Issue Type: Bug
Components: core
Affects Versions: 0.6.0
Environment: EC2, commandline whirr
Reporter: Paul Baclace
Priority: Critical
Whirr can fail to completely start a cluster and indicates this with a non-zero
return code. In many (currently intermittent) partial failure scenarios, there
are resources still active (EC2 machine instances, in my experience) that are
not cleaned up.
The log contains "IOException: Too many instance failed while bootstrapping!"
when I have seen orphaned nodes.
A non-zero return code should guarantee that all resources are cleaned up.
Without this post-condition, these failures require manual inspection and
cleanup to stop useless expenses (which is why I marked this bug critical; it
needs to be addressed for any kind of cron job triggered whirr).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
