+++ This bug was initially created as a clone of Bug #1766747 +++ Description of problem: In the dashboards page you see a lot of activity from 1AM. In my case it's an illogical time since this setup has just been installed. Version-Release number of selected component (if applicable): 4.3.0-0.ci-2019-10-29-152254 How reproducible: Unknown Steps to Reproduce: 1. Look at the activity card in the dashboards page. Actual results: Illogical timestamps Additional info: Screenshot attached --- Additional comment from Rastislav Wagner on 2019-11-04 08:56:59 UTC --- I also saw this once and the issue was that the event itself has a wrong timestamp (1.00 AM 1 January 1970). Can you take a look at the event itself if this is the same case ? If yes, than its not a bug in UI. --- Additional comment from Udi on 2019-11-06 14:44:46 UTC --- The timestamp is <unknown>: oc get events -n openshift-marketplace <unknown> Normal Scheduled pod/redhat-operators-7779d777f8-np5ph Successfully assigned openshift-marketplace/redhat-operators-7779d777f8-np5ph to rhhi-node-master-2 <unknown> Normal Scheduled pod/redhat-operators-784b69c4b8-d8pcv Successfully assigned openshift-marketplace/redhat-operators-784b69c4b8-d8pcv to rhhi-node-master-2 It's still a problem that in the UI these events are always at the top of the list (they're the most recent), and the timestamps are confusing in the GUI if they're from a different date. --- Additional comment from Samuel Padgett on 2019-11-12 14:22:09 UTC --- I'm going to change the component to kube-apiserver to investigate since these events should have timestamps, but also clone this bug to have console handle missing values.
This bug got cloned twice. We'll track under Bug 1772502 since it has an open PR. *** This bug has been marked as a duplicate of bug 1772502 ***