-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/41925/
-----------------------------------------------------------
(Updated Jan. 8, 2016, 3:46 p.m.)
Review request for Ambari, Robert Nettleton, Sandor Magyari, Sumit Mohanty, and
Sebastian Toader.
Bugs: AMBARI-14491
https://issues.apache.org/jira/browse/AMBARI-14491
Repository: ambari
Description (updated)
-------
With Blueprint deployments, zookeeper cannot be installed after manual upscale
(it can happen with any other services too).
That happened because of wrong cluster info.
Solution:
- check logical request state before adding them to the cluster info (as
pending components)
Diffs (updated)
-----
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
80d19d2
ambari-server/src/main/java/org/apache/ambari/server/utils/StageUtils.java
30843a4
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
035d6b1
ambari-server/src/test/java/org/apache/ambari/server/utils/StageUtilsTest.java
e1c47b9
Diff: https://reviews.apache.org/r/41925/diff/
Testing (updated)
-------
Unit tests done (SUCCESS).
Functional tests:
- deploy 1 node bp cluster (with zookeeper server). added 1 new host. install
zookeper server -> success.
- deploy 3-node cluster (namenode HA) -> move namenode -> cluster info is
correct (service check contains the correct nodes)
Thanks,
Oliver Szabo
