Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 19 Dec 2014 05:46:13 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12762711.1418943466000.66393.1418967973135@Atlassian.JIRA>
In-Reply-To: <JIRA.12762711.1418943466000@Atlassian.JIRA>
References: <JIRA.12762711.1418943466000@Atlassian.JIRA>
 <JIRA.12762711.1418943466961@arcas>
Subject: [jira] [Commented] (AMBARI-8806) Blueprints: Blueprints deployments
 failing due to missing Cluster ID in ClusterRequest
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on AMBARI-8806:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit-docker #541 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/541/])
AMBARI-8806. Blueprints deployments failing due to missing Cluster ID in ClusterRequest. (rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9e22e173102f15c2cfb181262fbfa8d8711423d2)
* ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java


> Blueprints: Blueprints deployments failing due to missing Cluster ID in ClusterRequest
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8806
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8806
>             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-8806.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> A recent patch checkin is causing Ambari Blueprints deployments to fail with a 500 HTTP error, with an error message complaining about the failure to update the configuration for the cluster. 
> The underlying problem is that the AmbariManagementControllerImpl has been modified to check for the ClusterRequest.getClusterID() field, and now throws an exception when this field is null.
> The Blueprints processor uses the ClusterRequest to update the configurations on a Blueprints-deployed cluster, and has historically never set the Cluster ID.
> The Blueprints processor or the management controller should be updated to handle this error differently, such that the Blueprints processor does not have to set the cluster ID, since the controller can still obtain the cluster information via the cluster name.
> I'm working on a patch to address this issue.  


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