ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez" <>
Subject Re: Review Request 38238: Bootstrap HDP 2.1 repo, cluster_version, and host_versions as CURRENT after upgrading Ambari
Date Thu, 10 Sep 2015 21:09:39 GMT

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

(Updated Sept. 10, 2015, 9:09 p.m.)

Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole,
and Sid Wagle.

Bugs: AMBARI-13001

Repository: ambari


In Ambari 2.1, if the stack is HDP 2.1, the user does not even see a Stacks and Versions page.
The Ambari upgrade will have to bootstrap the versions by
* Inserting repo_vesion for HDP 2.1
* Inserting cluster_vesion as CURRENT
* Inserting host_versions as CURRENT

This will then allow clicking on the "Perform Upgrade" button to call the Upgrades endpoint
correctly, which needs to know the source version in order to calculate the upgrade pack and
configs to use.

Diffs (updated)

  ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ d3326b1

  ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ 4382f59 
  ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ a2ff211

  ambari-server/src/main/java/org/apache/ambari/server/upgrade/ 6919e64

  ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml PRE-CREATION




Installed Ambari 2.1.1 with HDP
Upgraded Ambari to 2.1.2 using my build, which updated the schema, and also populated the
repo_version, cluster_version, and host_version.
In my install, only the repo_version had an id in the ambari_sequences table, so I also tested
that a value was inserted if not already present for all 3 entities.

I also added a basic upgrade pack for HDP 2.1 -> 2.3 for basic testing, which can be started
using a curl call.


Alejandro Fernandez

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