You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/12/03 03:00:14 UTC

[jira] [Commented] (AMBARI-14167) After Intra-Stack Upgrade Web Client Still Uses Old Stack Version In Requests

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

Srimanth Gunturi commented on AMBARI-14167:
-------------------------------------------

The reason this issue happens is that Ambari-UI caches the current stack model in memory. When the express upgrade finishes, all these models are still of the stale HDP-2.2 version. Thus when Storm service is added, information from HDP-2.2 is used in a HDP-2.3 environment - causing errors.

The fix is to reload Ambari-UI once express upgrade finishes.

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