ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8806) Blueprints: Blueprints deployments failing due to missing Cluster ID in ClusterRequest
Date Fri, 19 Dec 2014 02:58:14 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-8806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Nettleton updated AMBARI-8806:
-------------------------------------
    Attachment: AMBARI-8806.patch

Uploaded initial version of this patch

> 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)

Mime
View raw message