You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/09/04 15:57:00 UTC

[jira] [Commented] (AMBARI-24583) Ambari agent status could be reported stale just after execution command thread has finished execution

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

Hudson commented on AMBARI-24583:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #218 (See [https://builds.apache.org/job/Ambari-branch-2.7/218/])
AMBARI-24583. Ambari agent status could be reported stale just after (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=4d44151d8cfad305f118123066d4dd708be0c556])
* (edit) ambari-agent/src/main/python/ambari_agent/ComponentStatusExecutor.py


> Ambari agent status could be reported stale just after execution command thread has finished execution
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24583
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24583
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.2
>
>         Attachments: AMBARI-24583.patch
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)