[
https://issues.apache.org/jira/browse/AMBARI-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037233#comment-15037233
]
Hudson commented on AMBARI-14167:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3956 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3956/])
AMBARI-14167. After Intra-Stack Upgrade Web Client Still Uses Old Stack
(sgunturi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4fbdb31d97e380b475ff9c23dcec92f4567093d4])
* ambari-web/app/routes/stack_upgrade_routes.js
> After Intra-Stack Upgrade Web Client Still Uses Old Stack Version In Requests
> -----------------------------------------------------------------------------
>
> Key: AMBARI-14167
> URL: https://issues.apache.org/jira/browse/AMBARI-14167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.1.3
>
> Attachments: AMBARI-14167.patch
>
>
> After upgrading from HDP 2.2 to HDP 2.3, the web client is using the wrong
> stack version when making requests to endpoints like validation and
> recommendations.
> STR:
> 1) Install HDP 2.2 (ZooKeeper only is enough)
> 2) Perform Express Upgrade to HDP 2.3
> 3) Try to add a service, like Storm
> Observe:
> {code}
> Remote Address:[::1]:8080
> Request URL:http://localhost:8080/api/v1/stacks/HDP/versions/2.2/validations
> Request Method:POST
> Status Code:200 OK
> {code}
> and
> {code}
> Remote Address:[::1]:8080
> Request
> URL:http://localhost:8080/api/v1/stacks/HDP/versions/2.2/recommendations
> Request Method:POST
> Status Code:200 OK
> {code}
> This causes invalid recommendations and configurations when adding services
> after upgrade. If the user logs out and then back in, the correct version is
> used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
