ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22805) Blueprints do not handle some failures properly
Date Wed, 24 Jan 2018 16:12:00 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-22805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337825#comment-16337825
] 

Hudson commented on AMBARI-22805:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #581 (See [https://builds.apache.org/job/Ambari-branch-2.6/581/])
AMBARI-22805. Blueprints do not handle some failures properly - improve (6454655+adoroszlai:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c8921b6046aadc712ac4b389e825bc482129d40d])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/tasks/ConfigureClusterTask.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/AsyncCallableService.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/AsyncCallableServiceTest.java
AMBARI-22805. Blueprints do not handle some failures properly - fix (6454655+adoroszlai: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=51add1288529c2b28badf5737f50c40deb07e3a6])
* (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


> 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: 1h 20m
>  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)

Mime
View raw message