[
https://issues.apache.org/jira/browse/AMBARI-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830118#comment-15830118
]
Hudson commented on AMBARI-19560:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #761 (See
[https://builds.apache.org/job/Ambari-branch-2.5/761/])
AMBARI-19560. Timezone for timestamps in Upgrade History not consistent
(onechiporenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6061a677ed43cc354715de934789fa1b590897a0])
* (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js
* (edit)
ambari-web/test/views/main/admin/stack_upgrade/upgrade_history_view_test.js
> 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_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.4#6332)
