[AMBARI-21375] Pass Down More Specific Repository When Creating an Upgrade

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.5.2
• Fix Version/s: 2.5.2
• Component/s: ambari-web
• Epic Link: Cross Stack Name Upgrades
• Assignee: Andrii Tkach
• Reporter: Andrii Tkach
• Created: 29/Jun/17 15:10
• Updated: 11/Jul/17 17:21
• Resolved: 29/Jun/17 15:45

Description

The current command for creating an upgrade only passes in the version. It does not specify the stack that is associated with the version. This is because Ambari (incorrectly) assumes its the same stack.

Example of API call today

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"
  }
}

This needs to change to either supply the stack name along with the version or simply just the repository ID. It doesn't matter which one we switch to (the backend can adjust to either), but we should pick the easiest to change here since this is only going into Ambari 2.5.2.