Bug 1989961

Summary: CI apiserver downtime calculation isn't quite right
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: kube-apiserverAssignee: David Eads <deads>
Status: CLOSED ERRATA QA Contact: Ke Wang <kewang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.9CC: aos-bugs, mfojtik, xxia
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:44:29 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:

Description David Eads 2021-08-04 12:47:47 UTC
The minimum values don't reflect our detection capabilities, leading to undercount.  In addition, the times recorded are also incorrect.

Comment 2 Ke Wang 2021-08-17 02:07:13 UTC
$ w3m -dump -cols 200 'https://search.ci.openshift.org/?search=sig-api-machinery.*should+be+available&maxAge=336h&context=1&type=junit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job' | grep -E 'ms| 0s '

No results found.

Per PR changes,  from above search results, no longer see any time representation at the millisecond level and zero second in CI test results in past 13 days, so move the bug VERIFIED.

Comment 5 errata-xmlrpc 2021-10-18 17:44:29 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

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