The ComponentStatus resource appears to have a null creationTimestamp, when going to Explore -> ComponentStatus -> Instances I noticed they all report as "50 years ago". It looks like we are passing the null into the timestamp libraries and getting back epoch time. If i click into one of the instance the same problem happens on the details page expect I get the non-relative epoch time "Dec 31, 1969 7:00 pm"
It's an edge case that should generally not happen, as most resources do report a timestamp. ComponentStatus is a fake object and doesn't behave like normal k8s resources in this particular case.
Should handle the null another way with a N/A or some other way to show there is no timestamp.
Note: i actually found it in 4.4, but it's so minor it probably isn't worth a backport.
According to the fix, from PR's (https://github.com/openshift/console/pull/5283/files) comment, it is expected now.
Checked on 4.5.0-0.nightly-2020-05-06-003431
It returns the '-' when props.timestamp is null which is updated in the PR.
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.