[jira] [Updated] (AMBARI-11928) RU: UI does not specify from_version when downgrading

["Andrii Babiichuk (JIRA)" <ji...@apache.org>]

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

Andrii Babiichuk updated AMBARI-11928:
--------------------------------------
    Attachment: AMBARI-11928.patch

> RU:  UI does not specify from_version when downgrading
> ------------------------------------------------------
>
>                 Key: AMBARI-11928
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11928
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0.
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.0.
>
>         Attachments: AMBARI-11928.patch
>
>
> When the upgrade is cross-stack (HDP-2.2 -> HDP-2.3), the wrong upgrade pack is used to create tasks.
> When the user is presented an option to Downgrade, the following request is sent to the server:
> {noformat}
> POST /api/v1/clusters/c1/upgrades
> {
>   "RequestInfo": {
>     "downgrade": "true"
>   },
>   "Upgrade": {
>     "repository_version":"2.2.6.0-2772"
>   }
> }
> {noformat}
> This request makes the backend choose the HDP-2.2/upgrade-2.2 upgrade pack.  This is ok if the source and target versions were both 2.2, but when going from 2.2 to 2.3, we should be picking the upgrade-2.3 Upgrade Pack.  The request in this case should be:
> {noformat}
> POST /api/v1/clusters/c1/upgrades
> {
>   "RequestInfo": {
>     "downgrade": "true"
>   },
>   "Upgrade": {
>     "from_version": "2.3.0.0-2220",
>     "repository_version":"2.2.6.0-2772"
>   }
> }
> {noformat}
> The code to handle from_version is already implemented so no changes needed on the BE.



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