[
https://issues.apache.org/jira/browse/AMBARI-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824408#comment-15824408
]
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}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10077//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)
