[
https://issues.apache.org/jira/browse/AMBARI-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle resolved AMBARI-2320.
-------------------------------------
Resolution: Fixed
Committed to trunk.
> Ambari server should check agent machine can reach ambari server
> ----------------------------------------------------------------
>
> Key: AMBARI-2320
> URL: https://issues.apache.org/jira/browse/AMBARI-2320
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.5
> Reporter: Dmitry Lysnichenko
> Assignee: Myroslav Papirkovskyy
> Priority: Critical
> Fix For: 1.2.5
>
> Attachments: AMBARI-2320.patch
>
>
> Host registration commonly fails when Agent machine can't make it back to
> Server (results in failed host register because Server never sees host
> register).
> When using SSH to register hosts, Ambari server should confirm on the ambari
> agent host that it can reach the ambari server (check the web port of ambari
> server). If it can reach ambari server, then proceed with bootstrap process.
> If host cannot reach the ambari server, bail, do not start agent bootstraping
> and provide a message to the user "Host registration aborted. Ambari Agent
> host cannot reach Ambari Server. Please check the network connectivity
> between the Ambari Agent host and the Ambari Server"
> Other scenarios to consider:
> 1) the ambari server might have been configured to run on a port other than
> 8080 so the port to check should be passed down to the agent
> 2) how to handle authentication against the ambari server 8080? Can we just
> confirm we can connect to the port, even if auth fails? Connect is the test
> for connectivity, not actual results from the ambari server call.
--
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: http://www.atlassian.com/software/jira
