Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 10 May 2014 21:58:47 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12713390.1399669832572.316392.1399759127902@arcas>
In-Reply-To: <JIRA.12713390.1399669832572@arcas>
References: <JIRA.12713390.1399669832572@arcas>
Subject: [jira] [Updated] (AMBARI-5722) All Services Fail To Deploy Due To
 Agent Parsing Exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/AMBARI-5722?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley updated AMBARI-5722:
------------------------------------

    Priority: Critical  (was: Blocker)

> All Services Fail To Deploy Due To Agent Parsing Exception
> ----------------------------------------------------------
>
>                 Key: AMBARI-5722
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5722
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>         Environment: OSX (Ambari Server)
> CentOS 6.4 (Ambari Agents)
> The server must be deployed on a machine that is not part of the cluster =
to manifest this error.
>            Reporter: Jonathan Hurley
>            Priority: Critical
>             Fix For: 1.6.0
>
>
> When deploying a brand new cluster, all services fail to install due to a=
 parsing exception thrown from the Ambari Agents.
> File "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestr=
ator.py", line 113, in runCommand
> json_path =3D self.dump_command_to_json(command)
> File "/usr/lib/python2.6/site-packages/ambari_agent/CustomServiceOrchestr=
ator.py", line 209, in dump_command_to_json
> command'clusterHostInfo' =3D manifestGenerator.decompressClusterHostInfo(=
command'clusterHostInfo')
> File "/usr/lib/python2.6/site-packages/ambari_agent/manifestGenerator.py"=
, line 116, in decompressClusterHostInfo
> indexes =3D convertRangeToList(v)
> File "/usr/lib/python2.6/site-packages/ambari_agent/manifestGenerator.py"=
, line 57, in convertRangeToList
> raise AgentException.AgentException("Broken data in given range, expected=
 - ""m-n"" or ""m"", got : " + str(r))
> AgentException: 'Broken data in given range, expected - m-n or m, got : -=
1=E2=80=99
> The command being sent is
> {hs_host=3D[2], namenode_host=3D[1], snamenode_host=3D[2], zookeeper_host=
s=3D[0-2], ganglia_server_host=3D[1], nm_hosts=3D[0], ganglia_monitor_hosts=
=3D[0-2], all_hosts=3D[c6403.ambari.apache.org, c6401.ambari.apache.org, c6=
402.ambari.apache.org], rm_host=3D[2], app_timeline_server_hosts=3D[2], sla=
ve_hosts=3D[0], ambari_server_host=3D[-1], nagios_server_host=3D[1], all_pi=
ng_ports=3D[8670:0-2]}
> Notice the ambari-server-host which was added in that commit; it=E2=80=99=
s value is =E2=80=9C-1=E2=80=9D which would not parse correctly in manifest=
Generator.py
> I suspect Git e667dc7c9870864ff537374c819b7c1d1dd88e98 caused this proble=
m.
> Steps to reproduce:
> 1) Provision 3 c64 hosts
> 2) Wipe your server database and re-create it with the embedded PSQL scri=
pt
> 3) Attempt to provision a cluster with various services.
> All services will fail to deploy b/c of the above exception. This was wor=
king without issues before the above suspect commit.


--
This message was sent by Atlassian JIRA
(v6.2#6252)