[
https://issues.apache.org/jira/browse/AMBARI-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326954#comment-14326954
]
Hadoop QA commented on AMBARI-9696:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12699593/AMBARI-9696.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/1733//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1733//console
This message is automatically generated.
> RU - Ranger does not advertise a version
> ----------------------------------------
>
> Key: AMBARI-9696
> URL: https://issues.apache.org/jira/browse/AMBARI-9696
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.0
>
> Attachments: AMBARI-9696.patch
>
>
> Impact: Prevents RU from completing successfully
> Frequency: 100%
> STR:
> * Installed a 3-node cluster with ambari build #427
> * Installed HDP 2.2.2.0-2398 on centos 6
> * Added HDFS and ZK
> * Added Namenode HA
> * Add Ranger
> * Kerberized the cluster
> * Registered repo HDP 2.2.2.0-2399
> * Performed a RU
> This does not contain fix AMBARI-9683, so some components have a
> stale/incorrect version.
> However, the Ranger service does not have the capacity to advertise a version
> like the rest of the services.
> {code}
> ambari=> select component_name, host_name, version FROM hostcomponentstate
> WHERE version NOT LIKE '%99%' ORDER BY host_name, component_name;
> component_name | host_name | version
> -------------------+-------------------------+--------------
> KERBEROS_CLIENT | c6401.ambari.apache.org | 2.2.2.0-2398
> METRICS_MONITOR | c6401.ambari.apache.org | 2.2.2.0-2398
> RANGER_ADMIN | c6401.ambari.apache.org | UNKNOWN
> RANGER_USERSYNC | c6401.ambari.apache.org | UNKNOWN
> ZKFC | c6401.ambari.apache.org | 2.2.2.0-2398
> KERBEROS_CLIENT | c6402.ambari.apache.org | 2.2.2.0-2398
> METRICS_MONITOR | c6402.ambari.apache.org | 2.2.2.0-2398
> MYSQL_SERVER | c6402.ambari.apache.org | 2.2.2.0-2398
> ZKFC | c6402.ambari.apache.org | 2.2.2.0-2398
> KERBEROS_CLIENT | c6403.ambari.apache.org | 2.2.2.0-2398
> METRICS_COLLECTOR | c6403.ambari.apache.org | 2.2.2.0-2398
> METRICS_MONITOR | c6403.ambari.apache.org | 2.2.2.0-2398
> {code}
> This can be reproduced with just Ranger, and does not need a kerberized
> cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
