You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2015/04/29 05:13:05 UTC

[jira] [Resolved] (AMBARI-10811) Blueprints containing HA components or implicit MYSQL_SERVER components fail to provision

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

John Speidel resolved AMBARI-10811.
-----------------------------------
    Resolution: Fixed

merged to trunk

> Blueprints containing HA components or implicit MYSQL_SERVER components fail to provision
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10811
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10811
>             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  https://issues.apache.org/jira/browse/AMBARI-10750
> 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 configuration.



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