Bug 1802247

Summary: Bound token controller test flaking due to not waiting for operator readiness
Product: OpenShift Container Platform Reporter: Maru Newby <mnewby>
Component: kube-apiserverAssignee: Maru Newby <mnewby>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, mfojtik
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-13 21:57:54 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 Maru Newby 2020-02-12 17:38:36 UTC 
The TestBoundTokenSignerController/operator-secret-deletion is sometimes failing to succeed within the 10 minute timeout despite running in ~6m outside of CI:

=== RUN   TestBoundTokenSignerController
Found configuration for host https://api.ci-op-k4cwts09-61701.origin-ci-int-aws.dev.rhcloud.com:6443.
ClusterOperator/kube-apiserver: Available: true  Progressing: false  Degraded: false
--- FAIL: TestBoundTokenSignerController (611.45s)
            	Error Trace:	bound_sa_token_test.go:145
            	            				bound_sa_token_test.go:123
            	Error:      	Received unexpected error:
            	            	timed out waiting for the condition
            	Test:       	TestBoundTokenSignerController/operator-secret-deletion

When running tests locally I noticed that the test previous to this one (deletion of config map containing public keys used to verify bound tokens) could also trigger apiserver rollout which would need to complete before the next test should begin.
Comment 2 Xingxing Xia 2020-03-09 11:40:22 UTC 
PR is only for test code, not functional code. Moving to next status given MSTR-893 tested working well.
Comment 4 errata-xmlrpc 2020-05-13 21:57:54 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:0581