[
https://issues.apache.org/jira/browse/AMBARI-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198340#comment-14198340
]
Hadoop QA commented on AMBARI-8155:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12679521/AMBARI-8155.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 3 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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/505//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/505//console
This message is automatically generated.
> Nagios showing hdfs config types
> --------------------------------
>
> Key: AMBARI-8155
> URL: https://issues.apache.org/jira/browse/AMBARI-8155
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8155.patch
>
>
> During install, on Customize Services, you can get into a situation where the
> HDFS config types find their way onto the Nagios tab.
> Seems if you click to HDFS and then on Nagios, since HDFS has so many config
> types, if they haven't finished rendering on the page, they end up rendering
> on the Nagios tab.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
