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

Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2019/01/03 21:49:00 UTC

[jira] [Updated] (AMBARI-25086) Upgrading Using a Modified Default Version Repository Fails on Some Services

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

Jonathan Hurley updated AMBARI-25086:
-------------------------------------
    Summary: Upgrading Using a Modified Default Version Repository Fails on Some Services  (was: Trying to upgrade to 3.1 using the Default Version Definition fails)

> Upgrading Using a Modified Default Version Repository Fails on Some Services
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-25086
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25086
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 2.7.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Major
>             Fix For: 2.8.0
>
>
> When performing a stack upgrade, if the user chooses the "Default Version Definition" option and just modifies the default URLs, the backing VDF which is created and stored in the database contains which do not support upgrading. 
> Before the upgrade, if any of these services are in maintenance mode (such as Ambari Infra), they will prevent the upgrade from starting.
> During the actual upgrade, this will cause problems on finalization as those services/components have not participated, yet the VDF indicates that they should have.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)