Return-Path: <issues-return-25905-archive-asf-public=cust-asf.ponee.io@ambari.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id A5DEA200B89
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 21 Sep 2016 10:10:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id A4A3F160ACF; Wed, 21 Sep 2016 08:10:22 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id EBDA0160ADE
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 21 Sep 2016 10:10:21 +0200 (CEST)
Received: (qmail 97788 invoked by uid 500); 21 Sep 2016 08:10:21 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 97729 invoked by uid 99); 21 Sep 2016 08:10:21 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2016 08:10:21 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id D4DF92C2A63
	for <issues@ambari.apache.org>; Wed, 21 Sep 2016 08:10:20 +0000 (UTC)
Date: Wed, 21 Sep 2016 08:10:20 +0000 (UTC)
From: "Hari Sekhon (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13006423.1474445413000.624477.1474445420868@Atlassian.JIRA>
In-Reply-To: <JIRA.13006423.1474445413000@Atlassian.JIRA>
References: <JIRA.13006423.1474445413000@Atlassian.JIRA> <JIRA.13006423.1474445413519@arcas>
Subject: [jira] [Created] (AMBARI-18427) Agent 2.4.0.1 start error "cannot
 import name split_on_chunks" after upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Wed, 21 Sep 2016 08:10:22 -0000

Hari Sekhon created AMBARI-18427:
------------------------------------

             Summary: Agent 2.4.0.1 start error "cannot import name split_on_chunks" after upgrade
                 Key: AMBARI-18427
                 URL: https://issues.apache.org/jira/browse/AMBARI-18427
             Project: Ambari
          Issue Type: Bug
          Components: ambari-agent
    Affects Versions: 2.4.0
            Reporter: Hari Sekhon


I hit this issue yesterday after upgrading ambari-agent:
{code}
Verifying Python version compatibility...
Using python  /usr/bin/pythonChecking for previously running Ambari Agent...
Starting ambari-agentVerifying ambari-agent process status...
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}
I'm not the first person to have encountered it, see:

https://community.hortonworks.com/questions/55968/ambari-agent-start-failed-2.html

Considering this is an existing cluster the solution of rm -rf'ing the entire python2.6 site-packages seems excessive...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)