You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2017/03/20 22:05:42 UTC
[jira] [Updated] (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:all-tabpanel ]
Yusaku Sako updated AMBARI-19560:
---------------------------------
Reporter: Vivek Sharma (was: Oleg Nechiporenko)
> 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: Vivek Sharma
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19560_2.patch, AMBARI-19560_branch-2.5.patch, 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.15#6346)