Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 19 Jan 2017 10:07:26 +0000 (UTC)
From: "Oleg Nechiporenko (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13035161.1484558396000.50715.1484820446590@Atlassian.JIRA>
In-Reply-To: <JIRA.13035161.1484558396000@Atlassian.JIRA>
References: <JIRA.13035161.1484558396000@Atlassian.JIRA> <JIRA.13035161.1484558396358@jira-lw-us.apache.org>
Subject: [jira] [Reopened] (AMBARI-19560) Timezone for timestamps in Upgrade
 History not consistent with Background Operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 19 Jan 2017 10:07:32 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Nechiporenko reopened AMBARI-19560:
----------------------------------------

> 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
>
>
> 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)