[
https://issues.apache.org/jira/browse/AMBARI-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko resolved AMBARI-3871.
----------------------------------------
Resolution: Fixed
Committed to 1.4.2 and to trunk
> When adding nodes to an existing cluster yum should specify a specific
> ambari-agent version
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-3871
> URL: https://issues.apache.org/jira/browse/AMBARI-3871
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.5
> Reporter: Dmytro Shkvyra
> Assignee: Dmytro Shkvyra
> Fix For: 1.4.2
>
> Attachments: AMBARI-3871.patch
>
>
> When adding new nodes to an existing cluster that has outbound internet
> access yum install ambari-agent will grab the latest version of the agent
> causing registration to fail. The example is I have a 1.2 Ambari cluster, but
> 1.4 is the latest version. yum -y install ambari-agent will grab 1.4 instead
> of the cluster version 1.2. We just need to specify ambari-agent-1.2.
> Workaround is to have users manually install agents with the right version.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
