Bug 1906508

Summary:	TestHeaderNameCaseAdjust outputs nil error message on some failures
Product:	OpenShift Container Platform	Reporter:	Stephen Greene <sgreene>
Component:	Networking	Assignee:	Stephen Greene <sgreene>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	aos-bugs
Version:	4.7
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:41:51 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 Stephen Greene 2020-12-10 16:53:21 UTC

See https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-ingress-operator/505/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-operator/1337051993394384896#1:build-log.txt%3A156

When the new TestHeaderNameCaseAdjust operator e2e test fails to observe the expected output, no err is printed. This is because the original err variable from the wait.PollImmediate loop is overwritten by other error values when the test prepares error output information for failed runs.

The fix for this is trivial, however, and impact is low, since the only possible error message that could be displayed is a timeout message. However, it is a good idea to fix this test so any failures observed by other developers don't appear vague.

Comment 1 Stephen Greene 2020-12-10 16:54:59 UTC

See https://github.com/openshift/cluster-ingress-operator/blob/master/test/e2e/http_header_name_case_adjustment_test.go#L151-L171

Comment 5 errata-xmlrpc 2021-02-24 15:41:51 UTC

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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633