[
https://issues.apache.org/jira/browse/AMBARI-21141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028547#comment-16028547
]
Hudson commented on AMBARI-21141:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7549 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7549/])
AMBARI-21141 Web Client Is Using the Wrong Recommendations Endpoint When
(atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=64238cb9162f5098d2bafaa79999606f6c7abac3])
* (edit) ambari-web/app/utils/ajax/ajax.js
> Web Client Is Using the Wrong Recommendations Endpoint When Adding a Service
> ----------------------------------------------------------------------------
>
> Key: AMBARI-21141
> URL: https://issues.apache.org/jira/browse/AMBARI-21141
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 3.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: AMBARI-21141.patch
>
>
> When adding a service to an existing cluster, the web client is using the
> wrong recommendations endpoint.
> STR:
> - Install a simple 3-node cluster with ZooKeeper on HDP 2.5
> - Try to add Storm as a service
> - Notice that the recommendations being requested are from the 2.3 endpoint.
> This causes the Storm classes to be returned as {{org.backtype.}} instead of
> {{org.apache.storm.}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
