Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.4.2
-
None
Description
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.
[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
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 ====================
Attachments
Attachments
Issue Links
- links to