[ https://issues.apache.org/jira/browse/AMBARI-17251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laszlo Puskas updated AMBARI-17251: ----------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) > Client components that are dependencies of services in the stack definitions > are always added to blueprint deployments > ---------------------------------------------------------------------------------------------------------------------- > > Key: AMBARI-17251 > URL: https://issues.apache.org/jira/browse/AMBARI-17251 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Laszlo Puskas > Assignee: Laszlo Puskas > Fix For: 2.4.0 > > Attachments: AMBARI-17251.v1.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > h3. Problem: > Component dependencies from stack definitions are automatically added to > blueprint deployments even the services components belong to are not listed > in the blueprint. > eg. SPARK_CLIENT/TEZ_CLIENT components that are listed as dependencies of the > ATS and RESOURCEMANAGER in the stack definitions are always added to > blueprints. > h3. Solution > Component dependencies defined in stack definitions are only added to > blueprints if services belonging to the listed components are part of the > blueprint -- This message was sent by Atlassian JIRA (v6.3.4#6332)