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

Hadoop QA commented on AMBARI-12225:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12742943/AMBARI-12225.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 1 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:red}-1 core tests{color}.  The test build failed in 
contrib/views/slider 

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

This message is automatically generated.

> Unable to initialize Slider View on secure cluster with Wire Encryption
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-12225
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12225
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views, security
>    Affects Versions: 2.1.0
>         Environment: secured with wire encryption on, redhat 6.5
>            Reporter: Gour Saha
>         Attachments: AMBARI-12225.patch
>
>
> Throws the following exception -
> {code}
> Unable to initialize Slider view: javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException: PKIX path building failed: 
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
> valid certification path to requested target
> {code}



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

Reply via email to