test: [sig-auth][Feature:LDAP][Serial] ldap group sync can sync groups from ldap is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-auth%5C%5D%5C%5BFeature%3ALDAP%5C%5D%5C%5BSerial%5C%5D+ldap+group+sync+can+sync+groups+from+ldap fail [github.com/openshift/origin/test/extended/oauth/groupsync.go:32]: Unexpected error: <*errors.errorString | 0xc001bbea40>: { s: "replica for openldap-server not avaiable: timed out waiting for the condition", } replica for openldap-server not avaiable: timed out waiting for the condition occurred This test failure is happening on vsphere-ipi and vsphere-upi only. The pass rate of this test has gone down from over 90% to 70% and 40% respectively. https://sippy.ci.openshift.org/testdetails?release=4.6&test=%5Bsig-auth%5D%5BFeature%3ALDAP%5D%5BSerial%5D+ldap+group+sync+can+sync+groups+from+ldap
This is a fallout of the recent Docker image pull policies. The image used by the test is hosted on docker, not cached by the CI infra, even though it hasn't changed for the past 2 years, and when the limit of image pulls is reached, this test will just fail. I guess we'll have to find a different place for the image to live?
I'm on build watcher today, leaving this note for future build watchers, looks like similar issues are being seen across all releases for this an other auth tests (eg [sig-auth][Feature:SecurityContextConstraints] TestPodDefaultCapabilities). Docker pull rate limiting is causing havoc across the origin suite.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified.
I can see that the fixes from other BZs helped with this issue, I'm going to close the BZ as no longer relevant.