Bug 1763988 - [Suite:openshift/oauth] LDAP should start an OpenLDAP test server [Suite:openshift/conformance/parallel]
Summary: [Suite:openshift/oauth] LDAP should start an OpenLDAP test server [Suite:open...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: apiserver-auth
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Michal Fojtik
QA Contact: scheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-22 06:29 UTC by Wei Duan
Modified: 2020-02-04 09:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-04 09:43:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24042 0 'None' open Bug 1763988: ldap: extended timeout for run once pod to 8 minutes 2020-02-04 09:39:49 UTC
Github openshift origin pull 24082 0 'None' closed Bug 1763988: LDAP e2e: add dnf install retries, extend run timeout 2020-02-04 09:39:49 UTC

Description Wei Duan 2019-10-22 06:29:46 UTC
Description of problem:

https://testgrid.k8s.io/redhat-openshift-release-4.2-informing-ocp#release-openshift-ocp-installer-e2e-azure-4.2

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-4.2/136

fail [github.com/openshift/origin/test/extended/oauth/ldap.go:18]: Unexpected error:
    <*errors.errorString | 0xc0027997d0>: {
        s: "errours encountered trying to run ldapsearch pod: [error waiting for the pod 'runonce-ldapsearch-pod' to complete: timed out waiting for the condition]",
    }
    errours encountered trying to run ldapsearch pod: [error waiting for the pod 'runonce-ldapsearch-pod' to complete: timed out waiting for the condition]
occurred

Comment 1 Michal Fojtik 2019-11-06 19:49:58 UTC
There are PR's that should help us investigate why is this happening.

Comment 2 Standa Laznicka 2020-02-04 09:43:11 UTC
does not seem to be appearing that often anymore, and usually when most of the cluster (and all of the tests) is in total disarray


Note You need to log in before you can comment on or make changes to this bug.