[jira] [Commented] (AMBARI-13934) Request and Stage resources should refelect correct status after host delete

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on AMBARI-13934:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #3864 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3864/])
AMBARI-13934. Request and Stage resources should refelect correct status (swagle: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=63dab04d1ada4edc254e4ec3c18f95fbe36a016c])
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CalculatedStatus.java
* ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java
* ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionManager.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java


> Request and Stage resources should refelect correct status after host delete
> ----------------------------------------------------------------------------
>
>                 Key: AMBARI-13934
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13934
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13934.patch
>
>
> When you delete a host, it will delete all associated host_role_commands. During upgrade, if a host is deleted, then it is possible to have a Stage within the Upgrade request to have no tasks. Verify that it does not affect the upgrade operations.
> Possible issues:
> * A stage with no tasks should be declared as COMPLETED if not then it may result in the failure of the request
> * Some host_role_command (tasks) may be read once and then cached. Such cache, if they exist need to be refreshed



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