incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2099) Cluster install failed due to timeout and the user can proceed to cluster management; the user was not presented an option to retry install
Date Fri, 10 May 2013 18:43:19 GMT

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

Srimanth Gunturi commented on AMBARI-2099:
------------------------------------------

+1 for patch.
                
> Cluster install failed due to timeout and the user can proceed to cluster management;
the user was not presented an option to retry install
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-2099
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2099
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.3
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>            Priority: Critical
>             Fix For: 1.2.3
>
>         Attachments: AMBARI-2099_2.patch, AMBARI-2099.patch
>
>
> Installed a 4-node cluster.  The installation timed out, but UI went ahead and issued
the API call to start the services.  This resulted in a 500 server error (invalid transition
from INIT to STARTED).  UI should not have proceeded to Start, and should have presented the
option to Retry without letting the user move forward to manage a broken cluster.

--
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

Mime
View raw message