ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21141) Web Client Is Using the Wrong Recommendations Endpoint When Adding a Service
Date Mon, 29 May 2017 14:55:04 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028433#comment-16028433
] 

Aleksandr Kovalenko commented on AMBARI-21141:
----------------------------------------------

+1 for the patch

> 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)

Mime
View raw message