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

Hudson commented on AMBARI-17464:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #5175 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5175/])
AMBARI-17464 - Failed task status during EU is wrongly reported as (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bf5ca2f5e6714c8e0536504de9d54c8d6afc1425])
* 
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/HostRoleCommand.java
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Stage.java
* 
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
* 
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java


> Failed task status during EU is wrongly reported as SKIPPED_FAILED instead of 
> TIMED_OUT
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17464
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17464
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17464.patch
>
>
> # Deploy HDP 2.4 cluster
> # Start EU to 2.5.0.0 and wait for EU to reach till backup Hive DB prompt
> # At this point, stop Ambari agent on the "slave only" node (lets call the 
> host as host1)
> # Proceed with rest of the EU
> - The task - {{Stop Datanode}} (under Stop Core Components for Core Services 
> upgrade group) shows as {{HOLDING_TIMEDOUT}} for host1
> - Hit 'Ignore and Proceed' to continue further
> - The task - Restart HDFS/DATANODE shows as {{SKIPPED_FAILED}} and EU 
> continues to the next steps
> Caused by AMBARI-15671 - basically this is assuming that all tasks within a 
> stage follow the stage's auto skip setting, which is wrong. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to