[
https://issues.apache.org/jira/browse/AMBARI-12563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654314#comment-14654314
]
Hudson commented on AMBARI-12563:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #320 (See
[https://builds.apache.org/job/Ambari-branch-2.1/320/])
AMBARI-12563. Ambari alert return connection refuse because of motd (aonishuk)
(aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb8e925516231e912d88abf1bc642c35381a5e88)
*
ambari-common/src/main/python/resource_management/libraries/functions/curl_krb_request.py
> Ambari return fail upon service check
> --------------------------------------
>
> Key: AMBARI-12563
> URL: https://issues.apache.org/jira/browse/AMBARI-12563
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.1.1
>
>
> User has a third party monitoring tool that, whenever user do a
> 'su' it prints out the following message
> Hello user, have fun!
> Therefore, for example when user starts up namenode, Ambari is not able to
> phrase the status codes after executing the curl call for webHDFS, and throw
> error message and indicates the operation as fail. Meanwhile, the namenode is
> actually up and running.
> This behavior also happens across other services, such as HBase.
> This issue is causing confusion upon starting of
> services/components.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
