Bug 2047913

Summary: [sig-network][Feature:Router] The HAProxy router should override the route host for overridden domains with a custom value [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
Product: OpenShift Container Platform Reporter: Miciah Dashiel Butler Masters <mmasters>
Component: NetworkingAssignee: Miciah Dashiel Butler Masters <mmasters>
Networking sub component: router QA Contact: Arvind iyengar <aiyengar>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: urgent CC: dgoodwin, hongli, sippy
Version: 4.10   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 2047790 Environment:
Last Closed: 2022-08-23 19:39:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Miciah Dashiel Butler Masters 2022-01-28 20:45:01 UTC 
To resolve this BZ, https://github.com/openshift/origin/pull/26800 must be reverted and replaced with a change that enables the tests to pass and verify correct behavior on both FIPS and non-FIPS clusters.  

+++ This bug was initially created as a clone of Bug #2047790 +++

[sig-network][Feature:Router] The HAProxy router should override the route host for overridden domains with a custom value [Skipped:Disconnected] [Suite:openshift/conformance/parallel]

is perma in CI for aws fips, see:
https://sippy.ci.openshift.org/sippy-ng/tests/4.10/analysis?test=%5Bsig-network%5D%5BFeature%3ARouter%5D%20The%20HAProxy%20router%20should%20override%20the%20route%20host%20for%20overridden%20domains%20with%20a%20custom%20value%20%5BSkipped%3ADisconnected%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D

Slack thread: https://coreos.slack.com/archives/C01CQA76KMX/p1643324687239479

Problem already understood by team.

--- Additional comment from Devan Goodwin on 2022-01-28 14:51:13 UTC ---

Believed to just be a test issue, and ingress is actually working. Needs a quick fix to make sure we have signal, but not a blocker.
Comment 4 Arvind iyengar 2022-04-12 04:38:57 UTC 
With the fix in place the test case appears to be getting executed for FIPS enabled and non-fips environments:
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.11-informing#periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-fips
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.11-informing#periodic-ci-openshift-release-master-ci-4.11-e2e-aws
Comment 8 errata-xmlrpc 2022-08-23 19:39:39 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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-2022:5069