[
https://issues.apache.org/jira/browse/AMBARI-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130678#comment-14130678
]
Hudson commented on AMBARI-7242:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #221 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/221/])
AMBARI-7242. Make Nagios client dependencies conditional on client service
being deployed. (jspeidel:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9d201f548b3cc77745e6a7616cc2e7be8920dbe1)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BaseBlueprintProcessor.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BaseBlueprintProcessorTest.java
> Unnecessary conditional dependencies added to Blueprint when NAGIOS_SERVER
> included
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-7242
> URL: https://issues.apache.org/jira/browse/AMBARI-7242
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.6.1
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Fix For: 1.7.0
>
>
> If an Ambari Blueprint is posted that includes the "NAGIOS_SERVER" component
> in a host group definition, some YARN-related dependencies are automatically
> added to the blueprint, even if YARN is not referenced in the blueprint.
> This means that a blueprint may have slightly different content after a POST,
> so that the GET will return a blueprint with more components than originally
> desired.
> This problem is caused by the fact that some dependencies in Ambari are
> conditional, and this type of dependency is not yet modeled in the Ambari
> Stack Definitions. Whenever the NAGIOS_SERVER component is included, the
> dependencies associated with that component (including YARN_CLIENT,
> TEZ_CLIENT, etc) are also added to the blueprint during the creation process.
>
> The Blueprint handling code needs to be modified in order to handle this
> conditional type of dependency in the short term. As a longer-term fix,
> eventually these dependencies should be included in the stack definitions.
> I'll be posting a patch shortly that addresses this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
