Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1786564

Summary: Invalid timestamp on grafana "Kubernetes / Networking / Cluster" page
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Pawel Krupa <pkrupa>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: low    
Version: 4.3.0CC: alegrand, anpicker, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania, wzheng
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:21:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
time is invalid
none
removed time field from "Kubernetes / Networking / Cluster" none

Description Junqi Zhao 2019-12-26 09:32:29 UTC
Created attachment 1647670 [details]
time is invalid

Description of problem:
grafana "Kubernetes / Networking / Cluster" page, see the attached picture, "Current Bandwidth" panel
the time 1577352393000 is invalid
$ date --date='@1577352393000' -u
Fri Apr 23 10:30:00 UTC 51954

should be
$ date --date='@1577352393.000' -u
Thu Dec 26 09:26:33 UTC 2019


Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-25-185025

How reproducible:
always 

Steps to Reproduce:
1. Check grafana "Kubernetes / Networking / Cluster" page
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Pawel Krupa 2020-01-21 09:53:35 UTC
Seems like grafana multiplies value by 1000.

Comment 5 Junqi Zhao 2020-02-05 02:06:24 UTC
Created attachment 1657720 [details]
removed time field from "Kubernetes / Networking / Cluster"

Comment 10 errata-xmlrpc 2020-05-04 11:21:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581