You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2017/04/20 08:07:04 UTC

[jira] [Updated] (AMBARI-20787) Ambari agent should log how it determines it's FQDN

     [ https://issues.apache.org/jira/browse/AMBARI-20787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Toader updated AMBARI-20787:
--------------------------------------
    Fix Version/s:     (was: 2.5.1)
                   3.0.0

> Ambari agent should log how it determines it's FQDN
> ---------------------------------------------------
>
>                 Key: AMBARI-20787
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20787
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-agent
>    Affects Versions: 2.4.0
>            Reporter: Sebastian Toader
>            Assignee: Sebastian Toader
>             Fix For: 3.0.0
>
>
> Ambari agent determines its FQDN that will use for registering with Ambari Server as follows:
> # invokes the script specified by {{hostname_script}} in ambari-agent.ini and uses the output of this script as host name to register with.
> # if the script mentioned above returned with a non-zero error code (or threw an exception) than falls back to  [socket.getfqdn|https://docs.python.org/2/library/socket.html#socket.getfqdn] python api call.
> # if {{hostname_script}} is not set in  ambari-agent.ini than it uses [socket.getfqdn|https://docs.python.org/2/library/socket.html#socket.getfqdn] python api call.
> Currently the agent doesn't log anything about how it obtained its FQDN which makes troubleshooting difficult in case it registers with Ambari Server using unexpected/wrong FQDN.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)