[
https://issues.apache.org/jira/browse/AMBARI-11134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544011#comment-14544011
]
Hudson commented on AMBARI-11134:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2596 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2596/])
AMBARI-11134. Set service states when provisioning cluster via blueprint
(jspeidel:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9c570b859470e68427c399a870af426a3062ada9)
*
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
*
ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
> Blueprint provisioned clusters don't have service states updated
> ----------------------------------------------------------------
>
> Key: AMBARI-11134
> URL: https://issues.apache.org/jira/browse/AMBARI-11134
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
> Affects Versions: Ambari-2.1
> Reporter: John Speidel
> Assignee: John Speidel
> Labels: blueprints
> Fix For: Ambari-2.1
>
>
> Clusters that are provisioned via the REST API don't have service states
> updated. This doesn't affect the cluster starting and being operational but
> in cases where a component doesn't start, it isn't possible to start the
> component in the UI by starting the service. Starting the individual host
> component will work successfully.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
