You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/01/16 09:31:26 UTC
[jira] [Commented] (AMBARI-19560) Timezone for timestamps in
Upgrade History not consistent with Background Operations
[ https://issues.apache.org/jira/browse/AMBARI-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823682#comment-15823682 ]
Hadoop QA commented on AMBARI-19560:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12847597/AMBARI-19560.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10065//console
This message is automatically generated.
> Timezone for timestamps in Upgrade History not consistent with Background Operations
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-19560
> URL: https://issues.apache.org/jira/browse/AMBARI-19560
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19560.patch
>
>
> Looks like the timestamp in Upgrade History are shown as per current machine's timezone; while the timestamp entries in Background Operations Window is in GMT
> This causes confusion while trying to correlate events that happen after upgrade, as my machine's timezone is GMT+5.30, so the post upgrade events appear to show up few hours before the upgrade time reported in 'Upgrade History'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)