[ https://issues.apache.org/jira/browse/AMBARI-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260471#comment-15260471 ]
Hadoop QA commented on AMBARI-16129: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12801020/AMBARI-16129.patch.2 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 2 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 patch failed these unit tests in ambari-server: org.apache.ambari.server.state.cluster.ClusterTest Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6689//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6689//console This message is automatically generated. > LogSearch Integration using incorrect query parameters for LogSearch > -------------------------------------------------------------------- > > Key: AMBARI-16129 > URL: https://issues.apache.org/jira/browse/AMBARI-16129 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Robert Nettleton > Assignee: Robert Nettleton > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16129.patch.2 > > > The LogSearch integration layer in Ambari is passing incorrect query > parameters to the LogSearch Server. Recent multi-node testing has uncovered > this issue. > The LogSearch integration code should use "host_name" for specifying hosts in > query URLs, and "component_name" for specifying the component for a given > LogSearch query. The "component_name" change is related to a change in the > parameters for LogSearch itself, which used to use "components_name". > The integration code should be updated to use these query parameter names. > I'm working on a fix for this, and will be submitting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)