ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-10811) Blueprints containing HA components or implicit MYSQL_SERVER components fail to provision
Date Wed, 29 Apr 2015 02:17:06 GMT


Hudson commented on AMBARI-10811:

SUCCESS: Integrated in Ambari-trunk-Commit #2467 (See [])
AMBARI-10811. Fix issues with config topology update in certain topologies (jspeidel:
* ambari-server/src/main/java/org/apache/ambari/server/topology/
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/
* ambari-server/src/main/java/org/apache/ambari/server/topology/
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/

> Blueprints containing HA components or implicit MYSQL_SERVER components fail to provision
> -----------------------------------------------------------------------------------------
>                 Key: AMBARI-10811
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: blueprints
>    Affects Versions: Ambari-2.1
>            Reporter: John Speidel
>            Assignee: John Speidel
>            Priority: Blocker
>             Fix For: Ambari-2.1
> When provisioning a cluster using a blueprint that contains HA components or an existing
MYSQL_SERVER or implicit MYSQL_SERVER (not explicitly specified in blueprint but required
by dependency) the cluster fails to deploy.
> The request remains in the PENDING state and at 0% complete.
> Output like the following is logged to ambari-server.out:
> {code}
> TopologyManager.ConfigureClusterTask: Entering
> Caught an error from Config Processor: java.lang.IllegalArgumentException: Unable to
determine required host groups for component. Component 'MYSQL_SERVER' is not mapped to any
host group or is mapped to multiple groups.
> {code}
> This is a regression as a result of
> The problem was that the blueprint config processor was not dealing with these topologies
properly when trying to determine which host groups needed to be resolved prior to updating

This message was sent by Atlassian JIRA

View raw message