[
https://issues.apache.org/jira/browse/AMBARI-20122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047225#comment-16047225
]
Hudson commented on AMBARI-20122:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7617 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7617/])
Revert "AMBARI-20122 - Stack advisor needs to recommend dependency for (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=75152614e84299d16f36a6c6d7387b77a172eb96])
* (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
> Stack advisor needs to recommend dependency for slaves and masters
> ------------------------------------------------------------------
>
> Key: AMBARI-20122
> URL: https://issues.apache.org/jira/browse/AMBARI-20122
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Jaimin Jetly
> Assignee: Tim Thorpe
> Fix For: 3.0.0
>
> Attachments: AMBARI-20122.patch
>
>
> After resolution of AMBARI-19685, stack advisor validates if stack defined
> dependency is not satisfied but recommendation API does not account for this.
> Stack defined dependencies are service/component based and has a scope
> CLUSTER|HOST.
> During recommendation the services to install have already been selected. We
> can't really utilize the cluster scope because either the dependent service
> was selected or it was not. If it was not selected it will be caught during
> validation. We can only recommend based on HOST scope.
> This JIRA is also limited to only handling those which don't have conditional
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)