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.
PR is only for test code, not functional code. Moving to next status given MSTR-893 tested working well.
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