ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonenko Alexander (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21923) Web Client Should Only Show Revert Action On Revertable Repositories
Date Mon, 11 Sep 2017 09:38:00 GMT

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

Antonenko Alexander updated AMBARI-21923:
-----------------------------------------
    Attachment: AMBARI-21923_trunk.patch

> Web Client Should Only Show Revert Action On Revertable Repositories
> --------------------------------------------------------------------
>
>                 Key: AMBARI-21923
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21923
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.6.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-21923_branch26.patch, AMBARI-21923_trunk.patch
>
>
> Register, install, and apply several different PATCH repositories and the web client
allows each of them to be reverted in any order. The backend needs to provide a way to indicate
that only the most recent applied patch can be reverted.
> The backed should return a value, such as ClusterStackVersions/supports_revert which
clients, such as the web client, can use. 
> The backend will also now return ClusterStackVersions/revert_upgrade_id in the event
that the upgrade is revertable. This will fix a bug where the web client was choosing the
wrong upgrade to revert. This value should be used when making the call to the upgrades endpoint
Upgrade/revert_upgrade_id when initiating an upgrade reversion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message