Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 8 Jan 2015 18:31:36 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12765524.1420681400000.40390.1420741895990@Atlassian.JIRA>
In-Reply-To: <JIRA.12765524.1420681400000@Atlassian.JIRA>
References: <JIRA.12765524.1420681400000@Atlassian.JIRA>
 <JIRA.12765524.1420681400960@arcas>
Subject: [jira] [Commented] (AMBARI-9036) Deploying Storm via a Blueprint
 without Ganglia fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMBARI-9036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269821#comment-14269821 ] 

Hudson commented on AMBARI-9036:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #1431 (See [https://builds.apache.org/job/Ambari-trunk-Commit/1431/])
AMBARI-9036. Deploying Storm via a Blueprint without Ganglia fails. (rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a49cf5858fdda5446a6b2b7463d45d7985b076f9)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java


> Deploying Storm via a Blueprint without Ganglia fails
> -----------------------------------------------------
>
>                 Key: AMBARI-9036
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9036
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9036.patch
>
>
> Deploying a Blueprint that includes Storm will fail if the "GANGLIA_SERVER" component is not included in the Blueprint.
> The deployment error is:
> "{ "status" : 400, "message" : "Unable to update configuration property with topology information. Component 'GANGLIA_SERVER' is not mapped to any host group or is mapped to multiple groups." }"
> The Blueprint Configuration processor currently fails in this deployment scenario, while attempting to perform hostname substitution for some storm-site properties that reference the GANGLIA_SERVER component.  The configuration processor needs to be modified so that Storm can be deployed via a Blueprint without Ganglia. 
> I'm working on a fix for this, and will be submitting a patch shortly. 


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