Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 5 Jun 2014 17:53:01 +0000 (UTC)
From: "John Speidel (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12718690.1401990664211.77110.1401990781719@arcas>
In-Reply-To: <JIRA.12718690.1401990664211@arcas>
References: <JIRA.12718690.1401990664211@arcas>
Subject: [jira] [Created] (AMBARI-6041) Cluster create via blueprint fails
 when using an existing DB or hive metastore
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

John Speidel created AMBARI-6041:
------------------------------------

             Summary: Cluster create via blueprint fails when using an existing DB or hive metastore
                 Key: AMBARI-6041
                 URL: https://issues.apache.org/jira/browse/AMBARI-6041
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 1.6.0
            Reporter: John Speidel
            Assignee: John Speidel
             Fix For: 1.6.1


When deploying a cluster via a blueprint where the MYSQL_SERVER or HIVE_METASTORE are not included in the topology but are instead already existing, a 400 response is returned to the user even if the user properly configured the necessary configurations for an existing server.

{ 
"status" : 400, "message" : "Unable to update configuration properties with topology information. Component 'MYSQL_SERVER' is not mapped to any host group or is mapped to multiple groups." 
}

This occurs when deploying the cluster when the configurations are updated with topology related information. For components that may be external, we need to check if the user updated the default hostname or port in the corresponding configuration and if they have, don't do any topology update on the property.


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