ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12747) Ambari server upgrade does not re-extract the jar content of the views
Date Mon, 14 Sep 2015 22:07:46 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Yusaku Sako updated AMBARI-12747:
---------------------------------
    Assignee: Rohit Choudhary

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

Mime
View raw message