[jira] [Commented] (AMBARI-10331) BE issue: install repo version is stuck in INSTALLING after sudden server restart

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-10331:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12709025/AMBARI-10331.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2226//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2226//console

This message is automatically generated.

> BE issue: install repo version is stuck in INSTALLING after sudden server restart
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-10331
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10331
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10331.patch
>
>
> Installed the GA bits of champlain on 3node cluster on local vagrant.
> after the install is completed registered new version - 
> http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.2.2.0-2538
> while the install was in progress machine went down (including ambari-server) and once it was back up, noticed that install on host1 was completed and other 2 hosts were pending. Progress bar shows 'in progress' where as there were no background operations running. please see the screenshot attached. 
> the status of progress bar contradicts the bgops status.this could be intermittent as it might have happened because the machine went down when install was in progress. Please take a look.
> Since ambari-server went down, the server was unable to transition to cluster_version from INSTALLING->INSTALLED. This transition must happen while the version is running. The other transitions (e.g., UPGRADING->UPGRADED) happen because the agents advertise them.
> One way to fix this manually is to modify the DB by updating the cluster_version record from INSTALLING->OUT_OF_SYNC in order to retry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)