You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/08/13 05:04:46 UTC

[jira] [Commented] (AMBARI-12747) Ambari server upgrade does not re-extract the jar content of the views

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

Hudson commented on AMBARI-12747:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3271 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3271/])
AMBARI-12747. Ambari server upgrade does not re-extract the jar content of the views (Rohit Choudhary via srimanth) (sgunturi: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6dc98001f283b9eb0c52b9f47854ec4449f9ee89)
* ambari-server/src/main/python/ambari_server/serverUpgrade.py
* ambari-server/src/main/python/ambari_server/serverConfiguration.py


> Ambari server upgrade does not re-extract the jar content of the views
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-12747
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12747
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Rohit Choudhary
>            Priority: Critical
>             Fix For: 2.0.0, 2.1.0, 2.1.1
>
>         Attachments: AMBARI-12747_branch-2.1.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> *STR:*
> # Upgrade ambari-server from 2.0.0 to 2.1.0
> # Start ambari-server
> *Actual Result:* All view's jar are updated but previously extracted web resources are not updated
> *Expected Result:* All view's jar should be updated and views resources should be explicitly extracted to update the web content
> Due to this issue, user gets in a situation where views backend is updated but frontend is still using stale bits of earlier version which results in completely broken view in some cases.
> *workaround:*
> Manually stop ambari-server.
> Move the web resources of view to another location
> Start ambari-server back. This will re-extract the jar content and new web resources of the updated ambari version will be then used.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)