[jira] [Created] (AMBARI-21358) Upgrades Must Track To/From Repository Versions Instead of Strings

["Jonathan Hurley (JIRA)" <ji...@apache.org>]

Jonathan Hurley created AMBARI-21358:
----------------------------------------

             Summary: Upgrades Must Track To/From Repository Versions Instead of Strings
                 Key: AMBARI-21358
                 URL: https://issues.apache.org/jira/browse/AMBARI-21358
             Project: Ambari
          Issue Type: Task
    Affects Versions: 2.5.2
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Blocker
             Fix For: 2.5.2


When creating an upgrade in Ambari 2.5.x, the request appears as follows:

{code}
POST api/v1/clusters/c1/upgrades
{
  "Upgrade": {
    "repository_version": "2.6.0.0-334",
    "skip_failures": "true",
    "skip_service_check_failures": "true",
    "skip_prerequisite_checks": "true",
    "upgrade_type": "NON_ROLLING",
    "direction": "UPGRADE"
  }
}
{code}

The only identifier for the repository is the repo version. This forces the query to assume that the repository has the same name as the repository currently installed for the cluster. When going between stack vendors, this is incorrect:

STR:
- Install BigInsights 4.2.0 or 4.2.5
- Upgrade to Ambari 2.5.2
- Register HDP 2.6 and try to upgrade

The backend will look for {{BigInsights-2.6.0.0-1234}} instead of {{HDP-2.6.0.0-1234}}. A quick workaround is to fallback to a version-only search when the repository is not found. 

The fix for this is to allow the web client to pass the stack name in addition to the version. A repository ID can also be specified instead of the stack name/version.



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