ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alejandro Fernandez <>
Subject Review Request 43123: RU/EU should only delete configs on downgrade if source stack matches stack whose status is CURRENT
Date Wed, 03 Feb 2016 00:17:33 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole,
and Swapan Shridhar.

Bugs: AMBARI-14891

Repository: ambari


Saw a case with a customer in which they did the following.

* Ambari 2.1.2
* Rolling Upgrade from HDP 2.2 to and skipped the Finalize step, so Ambari never called
"Save DB State". Hence, the current stack version was still 2.2. They then modified the host_version
and cluster_version records in the DB to mark HDP 2.3 as CURRENT.
* Forgot to call ambari-server set-current-version
* Registered and installed bits for HDP and began another RU. After running into an
issue, they decided to downgrade, which then completely removed the configs for the target
stack (which is HDP 2.3!)

In order to prevent deleting configs in cases where the user has modified the database, add
stronger validation to FinalizeUpgradeAction so that we check that the request's source target
stack equals the stack of the repo marked as CURRENT. In this case, they were 2.2 and 2.3,





Ran unit tests in and verified on a live cluster


Alejandro Fernandez

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message