Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 27 Mar 2017 10:22:41 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13059318.1490602632000.129912.1490610161762@Atlassian.JIRA>
In-Reply-To: <JIRA.13059318.1490602632000@Atlassian.JIRA>
References: <JIRA.13059318.1490602632000@Atlassian.JIRA> <JIRA.13059318.1490602632917@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMBARI-20579) Ambari-server failed to stop
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 27 Mar 2017 10:22:46 -0000


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

Hadoop QA commented on AMBARI-20579:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12860616/AMBARI-20579.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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Ambari-server failed to stop
> ----------------------------
>
>                 Key: AMBARI-20579
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20579
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20579.patch
>
>
> STR:
>   1. Deploy HDP 2.3.6.0-3796 on Ambari 2.5.0.1
>   2. Enable NN HA
>   3. Remove ambari property "stack.upgrade.bypass.prechecks"
>   4. Add ambari property "stack.upgrade.bypass.prechecks" with value = "true"
>   5. Restart ambari-server  
> Result: Ambari-server failed to stop
> Cluster: 172.22.102.56 - nat-yc-r7-sgxs-ambari-hv-r-upg-19 - 48h
> Artifacts: <http://qelog.hortonworks.com/log/nat-yc-r7-sgxs-ambari-hv-r-upg-19
> /test-logs/ambari-hv-r-upg/ambaritestartifacts/artifacts/screenshots/com.hw.am
> bari.ui.tests.monitoring.admin_page.rolling_express_upgrade.TestRUPrechecksSki
> p/test040_PrerequisitesCheck/_22_4_1_42_Element_has_not_been_found_within_30_s
> econds__/>
>     
>     
>     Using python  /usr/bin/python
>     Restarting ambari-server
>     Waiting for server stop...
>     Ambari-server failed to stop
>     ERROR: Exiting with exit code 1. 
>     REASON: Ambari-server failed to stop
>     
>     [ERROR STREAM]
>     
>     
>     [EXIT CODE]
>     0


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)