[
https://issues.apache.org/jira/browse/AMBARI-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165089#comment-14165089
]
Hadoop QA commented on AMBARI-7691:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673882/AMBARI-7691_branch-1.7.0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/132//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/132//console
This message is automatically generated.
> Cluster state is lost when session is expired during cluster installation
> -------------------------------------------------------------------------
>
> Key: AMBARI-7691
> URL: https://issues.apache.org/jira/browse/AMBARI-7691
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Fix For: 1.7.0
>
> Attachments: AMBARI-7691.patch, AMBARI-7691_branch-1.7.0.patch, after
> relogin.png, empty installer.PNG
>
>
> STR:
> 1. Install cluster up to step {{Install, Start, and Test}}
> 2. Ensure that cluster is installed in fact (Green progress bar)
> 3. Wait some time to session get expired
> AR:
> Installer is broken, even after re-login. See the screenshot. Login, relogin,
> even {{localStorage.clean()}} does not help.
> ER:
> Cluster installer should go to already done step (Step Summary) after login.
> ---
> It looks like this is because we set Cluster state from UI but session is
> already expired and the request to update the cluster state does not reach
> the server, see BUG-21903 and comments there.
> Namely status of cluster is still {{INIT}} in database
> {code}
> select provisioning_state from clusters
> provisioning_state
> ------------------
> INIT
> {code}
> But actually cluster in installed and all services are running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
