[
https://issues.apache.org/jira/browse/AMBARI-11928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586361#comment-14586361
]
Hadoop QA commented on AMBARI-11928:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12739626/AMBARI-11928.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3186//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3186//console
This message is automatically generated.
> 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)
