[
https://issues.apache.org/jira/browse/AMBARI-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734158#comment-16734158
]
Hudson commented on AMBARI-25086:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10412 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10412/])
[AMBARI-25086] Upgrading Using a Modified Default Version Repository (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c20e418a2c0d278db6dea9caa5fd45cf6c80723d])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/repository/VersionDefinitionXml.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/repository/VersionDefinitionTest.java
> 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
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
