[WIP] Bug 1882853: Add cluster proxy settings to url tester exutil#25577
[WIP] Bug 1882853: Add cluster proxy settings to url tester exutil#25577sgreene570 wants to merge 5 commits intoopenshift:masterfrom
Conversation
|
@sgreene570: This pull request references Bugzilla bug 1882853, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sgreene570 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/bugzilla refresh |
|
@sgreene570: This pull request references Bugzilla bug 1882853, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/bugzilla refresh |
|
@sgreene570: This pull request references Bugzilla bug 1882853, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test e2e-aws-proxy |
1 similar comment
|
/test e2e-aws-proxy |
|
@sgreene570: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Proxy CI isnt feeling so well right now for unrelated reasons 🤒 https://coreos.slack.com/archives/CLJSH16J0/p1602173648085800 |
4b5dd57 to
4658821
Compare
|
/test e2e-aws-proxy |
1 similar comment
|
/test e2e-aws-proxy |
|
@sgreene570: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Doesn't fix the tests I thought it would |
|
@sgreene570: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@sgreene570: This pull request references Bugzilla bug 1882853. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Add a simple proxy util for fetching the cluster's egress proxy config.
Add's env vars to the url tester's execpod in test/extended/util/url/url.go so that the url tester can respect cluster-wide proxy settings during e2e tests.
Set the url tester to respect the cluster-wide proxy in test/extended/router/router.go.
Set the url tester to respect the cluster-wide proxy in test/extended/operators/routable.go
|
/reopen |
|
@sgreene570: Reopened this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@sgreene570: This pull request references Bugzilla bug 1882853, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
4658821 to
df991d0
Compare
|
might have missed something, testing my hunch out. Execpods for the url tester get re-used, so a test might have been creating the pod without the proxy env vars before tests that needed it even had the chance /test e2e-aws-proxy |
|
@sgreene570: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
I think the issue might be DNS resolution of the ELB /close |
|
@sgreene570: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR is an attempt to resolve https://bugzilla.redhat.com/show_bug.cgi?id=1882853 by having the url tester util in
test/extended/util/url/url.goapply available cluster proxy settings to the url tester execpod. Tests that utilize cluster ingress from within the cluster and utilize the url tester util can pass a proxy host to theTesterstruct via the newWithProxyfunction.This PR adds a helper function to get the cluster proxy config to the new
test/extended/util/proxy.gofile.openshift/release#12375 will allow this PR to be verified on the
e2e-aws-proxyjob.