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

Hadoop QA commented on AMBARI-19307:
------------------------------------

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

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

This message is automatically generated.

> UI should validate Ranger user password be more than 8 chars
> ------------------------------------------------------------
>
>                 Key: AMBARI-19307
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19307
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19307.patch
>
>
> During Ranger deploy, on config tab, user should set password for admin user. 
> UI do not validate password to be more than 8 characters. As the result, when 
> we will try to create it in Ranger, this user will not be valid (you can't 
> use this name/password to enter Ranger UI). Related alert will show critical 
> message. So, i think it should be fixed.



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

Reply via email to