Bug 1772125 - Conformance "should set Forwarded headers appropriately" router test is disabled on platforms except for Azure, AWS and GCP
Summary: Conformance "should set Forwarded headers appropriately" router test is disab...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Routing
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.4.0
Assignee: Dan Mace
QA Contact: Hongan Li
Depends On:
TreeView+ depends on / blocked
Reported: 2019-11-13 17:41 UTC by Andrew McDermott
Modified: 2020-02-21 14:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-02-21 14:53:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Andrew McDermott 2019-11-13 17:41:00 UTC
This is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1752646.

In BZ #1752646 we fixed the test but it is only known to work on Azure, AWS and GCP (looking at current CI results). This bug is to capture the fact that platforms outside those three are not currently being tested.

Comment 1 Andrew McDermott 2019-11-13 17:48:04 UTC
This is the PR that disabled the test for platforms NOT in AWS, Azure and GCP:


Comment 2 Martin André 2019-11-14 17:28:26 UTC
I had a look at the OpenStack platform today. In the example I looked, the test fails with `Unexpected header: '' (expected` where is the IP address of the worker node on the machine subnet.
We could look for the presence of `X-Forwarded-For` header as we're doing for AWS platform in https://github.com/openshift/origin/pull/24093/ and that should be OK. I don't think it's worth trying to be more specific and validate the IP address.

Comment 3 Dan Mace 2020-02-21 14:53:03 UTC
I'm going to go ahead and close this. We only manage a load balancer on AWS/Azure/GCP. For those platforms, we must support source IP preservation, and we are testing that. For other topologies, the user is responsible for the load balancer, so there's nothing for us to test in CI.

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