[
https://issues.apache.org/jira/browse/AMBARI-20536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938929#comment-15938929
]
Hadoop QA commented on AMBARI-20536:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12860187/AMBARI-20536.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-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11144//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11144//console
This message is automatically generated.
> Alerts Which Fallback To A Port In Absence of a URI Fail
> --------------------------------------------------------
>
> Key: AMBARI-20536
> URL: https://issues.apache.org/jira/browse/AMBARI-20536
> Project: Ambari
> Issue Type: Bug
> Reporter: Madhuvanthi Radhakrishnan
> Assignee: Madhuvanthi Radhakrishnan
> Fix For: 3.0.0
>
> Attachments: AMBARI-20536.patch
>
>
> AMBARI-20427 breaks the fallback behavior of WEB and METRIC alerts. In the
> event that a URI cannot be found, alerts will fallback to checking the
> default port of the current host.
> In the absence of yarn.nodemanager.webapp.address it will check 8042 which is
> the default port.
> However, the above change produces this error, which causes the port to not
> be parsed correctly:
> object has no attribute 'strip'
> This is because alert_uri.uri is an integer when its passed in.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
