You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/16 13:13:01 UTC
[jira] [Commented] (AMBARI-20536) Alerts Which Fallback To A Port
In Absence of a URI Fail
[ https://issues.apache.org/jira/browse/AMBARI-20536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366974#comment-16366974 ]
Hudson commented on AMBARI-20536:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-20536: Alerts Which Fallback To A Port In Absence of a URI Fail (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7f7938dcb6aee1ebfb80f85d258ea001b12deee0])
* (edit) ambari-common/src/main/python/resource_management/libraries/functions/get_port_from_url.py
* (edit) ambari-agent/src/test/python/resource_management/TestLibraryFunctions.py
> 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
> Priority: Major
> 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
(v7.6.3#76005)