Bug 1994643

Summary: kube-apiserver must not return 404 to garbage collection controller before being ready
Product: OpenShift Container Platform Reporter: Abu Kashem <akashem>
Component: kube-apiserverAssignee: Abu Kashem <akashem>
Status: CLOSED ERRATA QA Contact: Rahul Gangwar <rgangwar>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.9CC: aos-bugs, mfojtik, rgangwar, sttts, xxia
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-18 17:46:55 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 Abu Kashem 2021-08-17 15:39:36 UTC
Before kube-apiserver readiness, kube-controller-manager's GC and namespace controllers should not get a 404 for a resource or incomplete discovery because it will make them behave inconsistently by removed objects unexpectedly.

Comment 6 Abu Kashem 2021-09-01 13:58:01 UTC
moving it back to assigned, since we have a new pick from upstream.

Comment 12 errata-xmlrpc 2021-10-18 17:46:55 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.

https://access.redhat.com/errata/RHSA-2021:3759