ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yurii Shylov" <>
Subject Re: Review Request 30568: Rolling Upgrade Bootstrap - Allow Ambari upgrade from 1.7.0 - 2.0.0 to populate new tables
Date Wed, 11 Feb 2015 23:21:19 GMT

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

(Updated Фев. 11, 2015, 11:21 п.п.)

Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, and Nate Cole.


Final patch added, now it supports both 1.7->2.0 and RU workflow.

There was a problem with saving version to structured out on status commands. Agents use the
same file for every status command and thus even if version was written there once it is populated
for every status response. After RU was performed real version of could be overwritten
by old cached one which would cause finalize failure. It is hotfixed by removing version from
structured out if it was not requested.

Bugs: AMBARI-9054

Repository: ambari


During the upgrade process, populate the repo_version, cluster_version, and host_version tables.

Diffs (updated)

  ambari-common/src/main/python/resource_management/libraries/script/ 683397a 
  ambari-server/src/main/java/org/apache/ambari/server/agent/ a71bbd1

  ambari-server/src/main/java/org/apache/ambari/server/agent/ b60af2f

  ambari-server/src/main/java/org/apache/ambari/server/agent/ 4fe219c


Testing (updated)

UPD: manual testing done again. I couldn't get through finalize but it was caused by another
issue. Database state and logs show that patch doesn't make changes to regulare RU workflow.

Manual testing done, UT passing


Yurii Shylov

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