Bug 1764027

Summary: [Suite:openshift/oauth/htpasswd] HTPasswd IDP should successfully configure htpasswd and be responsive [Suite:openshift/conformance/parallel]
Product: OpenShift Container Platform Reporter: Wei Duan <wduan>
Component: apiserver-authAssignee: Stefan Schimanski <sttts>
Status: CLOSED DUPLICATE QA Contact: scheng
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, bparees, mfojtik, slaznick
Target Milestone: ---   
Target Release: 4.3.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: 2020-04-01 12:58:45 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 Wei Duan 2019-10-22 07:41:28 UTC
Description of problem:

https://testgrid.k8s.io/redhat-openshift-release-4.2-informing-ci#release-openshift-origin-installer-e2e-gcp-4.2


https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-4.2/154

[Suite:openshift/oauth/htpasswd] HTPasswd IDP should successfully configure htpasswd and be responsive [Suite:openshift/conformance/parallel]

fail [github.com/openshift/origin/test/extended/oauth/htpasswd.go:35]: Unexpected error:
    <*errors.errorString | 0xc0002713e0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred

Comment 2 Michal Fojtik 2019-11-06 19:48:18 UTC
Medium occurrence: https://ci-search-ci-search-next.svc.ci.openshift.org/?search=extended%2Foauth%2Fhtpasswd.go%3A35&maxAge=336h&context=2&type=all

Standa will probably know where to look.

Comment 3 Standa Laznicka 2019-11-07 09:47:38 UTC
Oleg, this is yet another case of the image being present but not being present in the same time. I recently had a cluster where I was able to reproduce this locally where each second pod of the oauth server deployment was unable to pull the same image the other pod could.

Comment 8 Standa Laznicka 2020-04-01 12:58:45 UTC

*** This bug has been marked as a duplicate of bug 1812662 ***