Bug 1776416

Summary: [FIPS] Test Failure: release-openshift-ocp-installer-e2e-aws-fips-4.3 #585 oc new-app should succeed with a --name of 58 characters [Suite:openshift/conformance/parallel/minimal]
Product: OpenShift Container Platform Reporter: Lokesh Mandvekar <lsm5>
Component: BuildAssignee: Gabe Montero <gmontero>
Status: CLOSED DUPLICATE QA Contact: wewang <wewang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, bparees, wking, wzheng
Target Milestone: ---   
Target Release: ---   
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: 2019-11-26 00:25:25 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:
Bug Depends On:    
Bug Blocks: 1752313    

Description Lokesh Mandvekar 2019-11-25 16:22:24 UTC 
Description of problem:

Please re-assign if installer isn't the right component.

See: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-fips-4.3/585

[Feature:Builds][Conformance] oc new-app should succeed with a --name of 58 characters [Suite:openshift/conformance/parallel/minimal] expand_less 	1m13s
fail [github.com/openshift/origin/test/extended/builds/new_app.go:56]: Unexpected error:
    <*errors.errorString | 0xc004b80310>: {
        s: "The build \"a234567890123456789012345678901234567890123456789012345678-1\" status is \"Failed\"",
    }
    The build "a234567890123456789012345678901234567890123456789012345678-1" status is "Failed"
occurred


Prior runs of release-openshift-ocp-installer-e2e-aws fail on different issues. This is the first occurrence of this failure in the past couple of days.
Comment 1 Lokesh Mandvekar 2019-11-25 16:26:55 UTC 
changing component to Build as per Mrunal's suggestion.
Comment 2 Lokesh Mandvekar 2019-11-25 19:47:01 UTC 
Don't see this issue anymore in the latest run at
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-fips-4.3/589

but I see timeout error waiting for secret deletion:

[Feature:OpenShiftControllerManager] TestDockercfgTokenDeletedController [Suite:openshift/conformance/parallel] expand_less 	5m17s
fail [github.com/onsi/ginkgo/internal/leafnodes/runner.go:64]: waiting for secret deletion: timed out waiting for the condition


The overall test shows green in prow though. I'll investigate the latest failure and file a new bug if necessary.
Comment 3 Ben Parees 2019-11-25 21:35:32 UTC 
Looks like we are still seeing issues w/ imagestreamtags resolving to the external registry instead of the internal registry, resulting in an authentication failure.
Comment 4 W. Trevor King 2019-11-26 00:25:25 UTC 
From the full build log [1], causal error was:

  2019-11-25T12:10:19.946189082Z F1125 12:10:19.946129       1 helpers.go:114] error: build error: After retrying 2 times, Pull image still failed due to error: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication

so I think this is a dup of bug 1775973.  Feel free to reopen if I'm wrong...

[1]: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-fips-4.3/585/build-log.txt

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