[AMBARI-17251] Client components that are dependencies of services in the stack definitions are always added to blueprint deployments

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Assignee: Laszlo Puskas
• Reporter: Laszlo Puskas
• Created: 15/Jun/16 12:01
• Updated: 16/Jun/16 14:51
• Resolved: 16/Jun/16 14:16

Description

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.

Solution

Component dependencies defined in stack definitions are only added to blueprints if services belonging to the listed components are part of the blueprint

Issue Links

• links to: Review Board