ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-21389) Cluster and Host Versions Can Change to CURRENT on their Own During an Upgrade
Date Sat, 01 Jul 2017 00:15:01 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-21389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hurley updated AMBARI-21389:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Cluster and Host Versions Can Change to CURRENT on their Own During an Upgrade
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-21389
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21389
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>             Fix For: 2.5.2
>
>         Attachments: AMBARI-21389.patch
>
>
> AMBARI-21361 introduced some code from {{trunk}} which works correctly with patch/service
upgrades on that branch. However, on Ambari 2.5 ({{branch-2.5}}) it causes host versions and
cluster versions to transition incorrectly to {{CURRENT}} during the upgrade.
> This prevents finalization.



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

Mime
View raw message