Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2EB47200C01 for ; Thu, 19 Jan 2017 14:48:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2D5D0160B54; Thu, 19 Jan 2017 13:48:32 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 78BF5160B42 for ; Thu, 19 Jan 2017 14:48:31 +0100 (CET) Received: (qmail 38372 invoked by uid 500); 19 Jan 2017 13:48:30 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 38363 invoked by uid 99); 19 Jan 2017 13:48:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2017 13:48:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 42BF6C0D5B for ; Thu, 19 Jan 2017 13:48:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Yqfd80lyNRlM for ; Thu, 19 Jan 2017 13:48:29 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 56A4E5F3BC for ; Thu, 19 Jan 2017 13:48:29 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 331D2E8673 for ; Thu, 19 Jan 2017 13:48:27 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 93A4E2528B for ; Thu, 19 Jan 2017 13:48:26 +0000 (UTC) Date: Thu, 19 Jan 2017 13:48:26 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 19 Jan 2017 13:48:32 -0000 [ https://issues.apache.org/jira/browse/AMBARI-19560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829958#comment-15829958 ] Hudson commented on AMBARI-19560: --------------------------------- FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6493 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6493/]) 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=ee8bbfb008c1d261bc726c17b7fcc917fbf5a862]) * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_history_view_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.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)