[
https://issues.apache.org/jira/browse/AMBARI-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116447#comment-15116447
]
Hudson commented on AMBARI-13339:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4224 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4224/])
AMBARI-13339. Failure To Create A Rolling Upgrade Leaves an Incorrect
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e26775eddaeb4b83f1fc13591d116a50e94d263b])
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractControllerResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/ControllerModule.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/DefaultProviderModule.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/ResourceProviderFactory.java
> Failure To Create A Rolling Upgrade Leaves an Incorrect Desired State
> ---------------------------------------------------------------------
>
> Key: AMBARI-13339
> URL: https://issues.apache.org/jira/browse/AMBARI-13339
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-13339.patch
>
>
> When creating an upgrade between stack versions (such as HDP 2.2 to 2.3), if
> the creation of the upgrade fails, then the following data is left in an
> inconsistent state:
> - Cluster Desired Version (still at 2.3)
> - Configurations: all new configurations created for 2.3 remain and are set
> as the desired configuration.
> We need to cleanup this data so that a failure to begin the upgrade doesn't
> leave the cluster in a bad state.
> STR:
> - Install HDP 2.2
> - Get ready to install HDP 2.3 by distributing the repo and resolving pre-req
> checks
> - Determine how you want to cause the failure. In my case, it was a problem
> while creating all of the states and tasks in the database.
> - Try to upgrade; the upgrade will never get created, but all of the 2.3
> configs will and the desired states will change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
