ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez" <afernan...@hortonworks.com>
Subject Re: Review Request 39306: AMBARI-13418. Stop-and-Start Upgrade: Upgrade START call cannot find upgrade pack to use
Date Wed, 14 Oct 2015 18:00:08 GMT


> On Oct. 14, 2015, 3:01 a.m., Dmytro Grinenko wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java, line
203
> > <https://reviews.apache.org/r/39306/diff/2/?file=1097966#file1097966line203>
> >
> >     Problably this required for unit-tests, but this also open possibility to override
upgrade packs version check for the user via API

Code needs to handle this option. UI is not going to specify it, so only a savvy user would
be able to add another upgrade pack of the same type and call the one he/she wants, which
is actually a valid use case in the future for someone that wants to customize an UpgradePack.


- Alejandro


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39306/#review102574
-----------------------------------------------------------


On Oct. 14, 2015, 2:42 a.m., Alejandro Fernandez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39306/
> -----------------------------------------------------------
> 
> (Updated Oct. 14, 2015, 2:42 a.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan Hurley, and
Nate Cole.
> 
> 
> Bugs: AMBARI-13418
>     https://issues.apache.org/jira/browse/AMBARI-13418
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Rolling Upgrade and Express Upgrade cannot be started because it cannot find the correct
upgrade pack to use based on the type.
> The PreChecks endpoint needs to resolve to the same upgrade pack.
> 
> 
> Diffs
> -----
> 
>   ambari-server/src/main/java/org/apache/ambari/server/controller/internal/PreUpgradeCheckResourceProvider.java
93093d2 
>   ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
bf7647e 
>   ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeHelper.java f0b383c

>   ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
066c0e6 
>   ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java 483a024

>   ambari-server/src/test/resources/stacks/HDP/2.1.1/upgrades/upgrade_test.xml 827348a

> 
> Diff: https://reviews.apache.org/r/39306/diff/
> 
> 
> Testing
> -------
> 
> Tested this on Ambari 2.1.3 using branch-2.1 and
> 1. HDP 2.1 can report a failure during the NON_ROLLING PreCheck if masters are down.
> 2. HDP 2.1->2.3 can pass the prechecks and start Express Upgrade
> 3. HDP 2.2 can report a failure during the ROLLING PreCheck if masters are down.
> 4. HDP 2.2->2.3 can pass the prechecks and start Rolling Upgrade
> 
> 
> For the Pre-Checks, tested using these endpoints,
> * http://server.:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*&UpgradeChecks/repository_version=2.3.2.0-2950&UpgradeChecks/upgrade_type=ROLLING
> * http://server.:8080/api/v1/clusters/c1/rolling_upgrades_check?fields=*&UpgradeChecks/repository_version=2.3.2.0-2950&UpgradeChecks/upgrade_type=NON_ROLLING
> 
> 
> I tagged some of the unit tests with Ignore since they were failing in an unrelated area
due to the setup.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>


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