ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Tkach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21375) Pass Down More Specific Repository When Creating an Upgrade
Date Thu, 29 Jun 2017 15:15:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-21375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068458#comment-16068458
] 

Andrii Tkach commented on AMBARI-21375:
---------------------------------------

30378 passing (25s)
  157 pending

> Pass Down More Specific Repository When Creating an Upgrade
> -----------------------------------------------------------
>
>                 Key: AMBARI-21375
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21375
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.5.2
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.5.2
>
>         Attachments: AMABRI-21375.patch
>
>
> 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.
> {code:title=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"
>   }
> }
> {code}
> 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.



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

Mime
View raw message