Bug 1998516

Summary:	openshift-apiserver should not set Available=False APIServicesAvailable on update
Product:	OpenShift Container Platform	Reporter:	Wally <wlewis>
Component:	openshift-apiserver	Assignee:	Lukasz Szaszkiewicz <lszaszki>
Status:	CLOSED WONTFIX	QA Contact:	Xingxing Xia <xxia>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.8	CC:	mfojtik, wking
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	tag-ci
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-16 11:36:58 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:

Description Wally 2021-08-27 13:01:45 UTC

This BZ will address the 3rd error category described here - https://bugzilla.redhat.com/show_bug.cgi?id=1948089#c20



3."failing or missing response from an aggregated API ... context deadline exceeded" error - reported by the Kube API server status controller.

https://search.ci.openshift.org/?search=clusteroperator%2Fopenshift-apiserver+condition%2FAvailable+status%2FFalse+reason%2FAPIServicesAvailable.*Get.*8443%2Fapis.*context&maxAge=24h&context=1&type=junit&name=periodic.*4.9.*upgrade&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Comment 1 Lukasz Szaszkiewicz 2021-09-02 11:50:16 UTC

we should also try to fix clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: etcdserver: leader changed errors

https://search.ci.openshift.org/?search=clusteroperator%2Fopenshift-apiserver+condition%2FAvailable+status%2FFalse+reason%2FAPIServicesAvailable.*&maxAge=24h&context=1&type=junit&name=periodic.*4.9.*upgrade&excludeName=4.8%7Csingle-node&maxMatches=5&maxBytes=20971520&groupBy=job

Comment 2 Wally 2021-09-20 20:17:44 UTC

Setting to --- for proper prioritization during 4.10

Comment 3 Lukasz Szaszkiewicz 2021-10-13 10:23:28 UTC

taking only upgrades to 4.10 into account and excluding SNO and OVN it looks like the issue is rare.

https://search.ci.openshift.org/?search=clusteroperator%2Fopenshift-apiserver+condition%2FAvailable+status%2FFalse+reason%2FAPIServicesAvailable.*&maxAge=24h&context=1&type=junit&name=periodic.*4.10.*upgrade&excludeName=4.9%7Csingle-node%7Covn&maxMatches=5&maxBytes=20971520&groupBy=job

Comment 5 Michal Fojtik 2023-01-16 11:36:58 UTC

Dear reporter, we greatly appreciate the bug you have reported here. Unfortunately, due to migration to a new issue-tracking system (https://issues.redhat.com/), we cannot continue triaging bugs reported in Bugzilla. Since this bug has been stale for multiple days, we, therefore, decided to close this bug.
If you think this is a mistake or this bug has a higher priority or severity as set today, please feel free to reopen this bug and tell us why. We are going to move every re-opened bug to https://issues.redhat.com. 

Thank you for your patience and understanding.