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

Hadoop QA commented on AMBARI-20308:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12855933/AMBARI-20308.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/10882//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10882//console

This message is automatically generated.

> Atlas service check fails during EU on wire encrypted cluster
> -------------------------------------------------------------
>
>                 Key: AMBARI-20308
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20308
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Vivek Sharma
>            Assignee: Jonathan Hurley
>            Priority: Critical
>              Labels: express_upgrade
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20308.patch
>
>
> STR
> 1. Deployed cluster with Ambari version: 2.4.2.0-136 and HDP version: 
> 2.5.3.0-37 (wire encrypted cluster)
> 2. Upgrade Ambari to 2.5.0.0-1030 and then start EU to 2.6
> 3. Observed following failure at Atlas service check
> {code}
> 2017-03-02 13:22:41,729 - ATLAS service check failed for host atlas_host with 
> error Execution of 'curl -k --negotiate -u : -b ~/cookiejar.txt -c 
> ~/cookiejar.txt -s -o /dev/null -w "%{http_code}" https://atlas_host:21443/' 
> returned 35. ######## Hortonworks #############
> This is MOTD message, added for testing in qe infra
> 000
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py",
>  line 52, in <module>
>     AtlasServiceCheck().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 313, in execute
>     method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py",
>  line 48, in service_check
>     raise Fail("All instances of ATLAS METADATA SERVER are down.")
> resource_management.core.exceptions.Fail: All instances of ATLAS METADATA 
> SERVER are down.
> {code}



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

Reply via email to