[
https://issues.apache.org/jira/browse/AMBARI-21914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-21914:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.6
> Agent on ambari-server host does not start when server is not upgraded
> ----------------------------------------------------------------------
>
> Key: AMBARI-21914
> URL: https://issues.apache.org/jira/browse/AMBARI-21914
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Affects Versions: 2.4.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21914.patch
>
>
> This was a customer upgrade from Ambari-2.2.2 to Ambari-2.4.2. We should
> investigate why the behavior is different for hosts with ambari-server. It's
> better to have the same PYTHON_PATH or library resolution scheme for the
> agent irrespective of the host it is installed.
> {code}[root@c6401 vagrant]# yum list installed | grep ambari
> ambari-agent.x86_64 2.4.2.0-136 @Updates-ambari-2.4.2.0
> ambari-server.x86_64 2.2.2.0-460 @Updates-ambari-2.2.2.0{code}
> {code}ERROR: ambari-agent start failed. For more details, see
> /var/log/ambari-agent/ambari-agent.out:
> ====================
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/ambari_agent/AmbariAgent.py", line
> 24, in <module>
> from Controller import AGENT_AUTO_RESTART_EXIT_CODE
> File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line
> 41, in <module>
> from ambari_agent.ActionQueue import ActionQueue
> File "/usr/lib/python2.6/site-packages/ambari_agent/ActionQueue.py", line
> 37, in <module>
> from ambari_commons.str_utils import split_on_chunks
> ImportError: cannot import name split_on_chunks
> ===================={code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
