[
https://issues.apache.org/jira/browse/AMBARI-22805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338892#comment-16338892
]
Hudson commented on AMBARI-22805:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8636 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8636/])
AMBARI-22805. Improve Blueprints error handling in case of timeout (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=947d7e74c732e67c01d245f030b9af2d871c2c0b])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/AsyncCallableServiceTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/AsyncCallableService.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/ConfigureClusterTask.java
> Blueprints do not handle some failures properly
> -----------------------------------------------
>
> Key: AMBARI-22805
> URL: https://issues.apache.org/jira/browse/AMBARI-22805
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Critical
> Labels: blueprints, pull-request-available
> Fix For: 3.0.0, 2.6.2
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Failures in the cluster configuration task and topology host tasks during
> blueprint cluster deployment or upscaling are not visible via request status.
> The logical request stays PENDING even after Ambari Server gave up retrying.
> Both the fact that it no longer makes progress and any reason of the failure
> can be seen only in {{ambari-server.log}}.
> Some ways to reproduce (all via blueprints):
> * Create cluster with ZooKeeper and HDFS, but omit the NAMENODE component
> * Create a secure cluster with wrong Kerberos credentials
> * Create a secure cluster without storing Kerberos credentials, restart
> Ambari Server, add a new node
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
