-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/49260/
-----------------------------------------------------------
(Updated June 29, 2016, 9:10 a.m.)
Review request for Ambari, Daniel Gergely, Oliver Szabo, Robert Nettleton, and
Sandor Magyari.
Bugs: AMBARI-17313
https://issues.apache.org/jira/browse/AMBARI-17313
Repository: ambari
Description
-------
Problem:
In case services / components are restarted, their desired states are not
changed. As during restart -per definition- services are expected to be in
STARTED state this should be OK, however if the restart is triggered for
services in STOPPED state this causes problems (The UI allows triggering
restart for stopped services). (Eg.: recovery manager doesn't bring them back
to running state)
Solution:
When assembling the RESTART custom command desired states of affected services
are updated to STARTED.
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
b60592d
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelperTest.java
68b31c0
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
fd70df5
Diff: https://reviews.apache.org/r/49260/diff/
Testing (updated)
-------
Manually tested on dev-env.
Unit tests passed.
Thanks,
Laszlo Puskas
