ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (JIRA)" <>
Subject [jira] [Updated] (AMBARI-2319) Perform hostname comparison before registering the agent
Date Fri, 06 Sep 2013 18:07:59 GMT


Mahadev konar updated AMBARI-2319:

    Fix Version/s:     (was: 1.2.5)
> Perform hostname comparison before registering the agent
> --------------------------------------------------------
>                 Key: AMBARI-2319
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.5
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>            Priority: Critical
>             Fix For: 1.4.1
> Host registration commonly fails when Agent machine registers with Server under a different
hostname than Server expected (results in failed register because Server thinks host never
> This is when the Agent machine hostname is not set properly (or set differently than
how Ambari server expects), so the Ambari server never sees the Agent registration return,
resulting in a failed registration.
> Need to make this scenario 1) easier to troubleshoot 2) more clear to the user 3) provide
paths out of this situation (warn, retry, remove)
> Proposal:
> - When using SSH to register hosts, Ambari server should send down expected hostname
during bootstrap. For example, user enters in the UI.
> - Ambari server connects to, then starts the agent setup process.
Once the agent determines what hostname it will register as (via figuring out fqdn), it should
confirm that it matches
> - In the case where those match, Agent is started and proceeds with registration.
> - In the case where those do not match, Agent writes to log "ambari agent machine hostname
does not match expected ambari server hostname. Aborting registration. Please check hostname,
hostname -f and /etc/hosts file to confirm your hostname is setup correctly"
> - Also, in the do not match case, the ambari server will indicated "Failed" on registration.
That should also include a message "Registration failed. Please check the Ambari Agent log
on the <target host> as /var/log/ambari-agent/ambari-agent.log for more information"
> On manual agent registration, since there is to "expected" hostname (since the agent
registration was not initiated by the ambari server), the agent should just register as normal
(as it does today).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message