Bug 1822514

Summary: API upgrade monitoring in CI should distinguish between kube and openshift APIs
Product: OpenShift Container Platform Reporter: Stefan Schimanski <sttts>
Component: kube-apiserverAssignee: Stefan Schimanski <sttts>
Status: CLOSED ERRATA QA Contact: Ke Wang <kewang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, kewang, mfojtik
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1822515 (view as bug list) Environment:
Last Closed: 2020-07-13 17:26:34 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:
Bug Depends On:    
Bug Blocks: 1822515    

Description Stefan Schimanski 2020-04-09 08:54:25 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Ke Wang 2020-04-14 07:06:07 UTC 
Per PR https://github.com/openshift/origin/pull/24844, I compared two upgrade api testing CI jobs, one is not fixed https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/20000/artifacts/e2e-aws-upgrade/container-logs/test.log

another is fixed with OCP build 4.5.0-0.nightly-2020-04-13-060619 which found the following in log https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/25503/artifacts/e2e-aws-upgrade/container-logs/test.log,
,
STEP: Building a namespace api object, basename openshift-api-available
STEP: Building a namespace api object, basename kubernetes-api-available

They were new as mentioned in PR. So the bug has been fixed, move it verify.
Comment 4 errata-xmlrpc 2020-07-13 17:26:34 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:2409