You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Jayush Luniya (JIRA)" <ji...@apache.org> on 2016/06/15 04:28:09 UTC

[jira] [Commented] (AMBARI-17233) Upgrade management packs should handle build numbers gracefully

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

Jayush Luniya commented on AMBARI-17233:
----------------------------------------

Branch-2.4
commit 402b9d3031fe3bfcca8126c13d24aaf93766abf0
Author: Jayush Luniya <jl...@hortonworks.com>
Date:   Tue Jun 14 21:26:00 2016 -0700

    AMBARI-17233: Upgrade management packs should handle build numbers gracefully (jluniya)

> Upgrade management packs should handle build numbers gracefully
> ---------------------------------------------------------------
>
>                 Key: AMBARI-17233
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17233
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17233.patch
>
>
> Build numbers in mpack version <major>.<minor>.<maint>.<patch>-<buildnum> should be handled gracefully when upgrading mpacks.
> ambari-server install-mpack --mpack=hdf-ambari-mpack-2.0.0.0-8.tar.gz --purge --verbose
> ambari-server upgrade-mpack --mpack=hdf-ambari-mpack-2.0.0.0-8.tar.gz  --verbose (Self upgrade should fail)
> ambari-server upgrade-mpack --mpack=hdf-ambari-mpack-2.0.0.0-12.tar.gz  --verbose (Build to build upgrade should fail)
> ambari-server upgrade-mpack --mpack=hdf-ambari-mpack-2.0.0.1-1.tar.gz  --verbose (Upgrade should succeed)



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