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
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
Setting to --- for proper prioritization during 4.10
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
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.