You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@whirr.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2012/12/07 21:51:21 UTC

[jira] [Commented] (WHIRR-684) auth failure could be reported as auth failure

    [ https://issues.apache.org/jira/browse/WHIRR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526760#comment-13526760 ] 

Steve Loughran commented on WHIRR-684:
--------------------------------------

Note also that whirr appears to hang
                
> auth failure could be reported as auth failure
> ----------------------------------------------
>
>                 Key: WHIRR-684
>                 URL: https://issues.apache.org/jira/browse/WHIRR-684
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.9.0
>         Environment: EC2 with a revoked AWS key
>            Reporter: Steve Loughran
>            Priority: Minor
>
> After revoking an AWS key, trying to start that cluster with an invalid key triggered an error about AMI retrieval, not "you can't log in"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira