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

Hadoop QA commented on AMBARI-7973:
-----------------------------------

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

This message is automatically generated.

> Knox configuration of users-ldif results in bad format of users.ldif file
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-7973
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7973
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 1.7.0
>            Reporter: Sumit Gupta
>            Assignee: Sumit Gupta
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7973.patch
>
>
> The bad format of the users.ldif file written out by the content of the 
> users-ldif configuration section results in the demo LDAP not reading the 
> configuration correctly and the guest user not being able to authenticate.



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

Reply via email to