[
https://issues.apache.org/jira/browse/AMBARI-11825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580150#comment-14580150
]
Shantanu Mundkur commented on AMBARI-11825:
-------------------------------------------
Tried using isComponentUsingCardinalityForLayout in the stack_advisor to see if
it made a difference for slaves/clients in this case but it did not seem to
help and there was still an attempt to create duplicate host_components.
> Failure to add or install component defined with cardinality ALL
> ----------------------------------------------------------------
>
> Key: AMBARI-11825
> URL: https://issues.apache.org/jira/browse/AMBARI-11825
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Shantanu Mundkur
> Fix For: 2.1.0
>
>
> A MASTER, SLAVE or CLIENT component defined with a cardinality of ALL results
> in a failure while adding the service, upon clicking Deploy, with an error
> like:
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Attempted to create host_component's which already exist:
> [clusterName=CLUSTER1, hostName=node1.domain.com,
> componentName=MYSERVICE_MASTER],[clusterName=CLUSTER1,
> hostName=node1.domain.com, componentName=MYSERVICE_MASTER]
> or
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException:
> Attempted to create a host_component which already exists:
> [clusterName=CLUSTER2, hostName=node10.domain.com,
> componentName=MYSERVICE_SLAVE]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
