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/02/28 10:11:00 UTC

[jira] [Commented] (AMBARI-23105) Exception caught while installing Timeline Service V2.0

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

Hudson commented on AMBARI-23105:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8784 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8784/])
AMBARI-23105. Exception caught while installing Timeline Service V2.0  (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ab97b5f6907ce4f8437d4ece455e7ee20d1096b1])
* (edit) ambari-agent/src/main/python/ambari_agent/ConfigurationBuilder.py
* (edit) ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py


> Exception caught while installing Timeline Service V2.0 
> --------------------------------------------------------
>
>                 Key: AMBARI-23105
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23105
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>         Attachments: AMBARI-23105.patch
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> While installing Timeline Service V2.0 during CI run, the following error is
> captured:
>     
>     
>     Caught an exception while executing custom service command: <type 'exceptions.Exception'>: Command requires configs with timestamp=1519782088331 but configs on agent have timestamp=1519783511993; Command requires configs with timestamp=1519782088331 but configs on agent have timestamp=1519783511993
>     
> See <http://172.27.30.209:8080> (up until 8pm ET 3/1)



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