Skip to content

test: skip tests that won't work behind a proxy automatically#26398

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
stbenjam:proxy
Sep 7, 2021
Merged

test: skip tests that won't work behind a proxy automatically#26398
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
stbenjam:proxy

Conversation

@stbenjam
Copy link
Member

The vast majority of the tests we run work and run fine through
an HTTP proxy to reach the target cluster under test, however a
handful of tests don't work. This adds a configuration to
openshift-tests to see if given the current proxy environment, we
would use a proxy to reach the API server. If so, then we skip
tests annotated with [Skip:Proxy].

@deads2k
Copy link
Contributor

deads2k commented Aug 16, 2021

I'd like to get the proxy job clean more than I'd like every test available

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 16, 2021
@stbenjam stbenjam changed the title test: skip tests that won't work behind a proxy automatically [wip] test: skip tests that won't work behind a proxy automatically Aug 16, 2021
@stbenjam
Copy link
Member Author

/hold

I just want to check one thing before this lands

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 16, 2021
@stbenjam stbenjam changed the title [wip] test: skip tests that won't work behind a proxy automatically test: skip tests that won't work behind a proxy automatically Aug 16, 2021
@openshift-ci openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Aug 16, 2021
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2021
The vast majority of the tests we run work and run fine through
an HTTP proxy to reach the target cluster under test, however a
handful of tests don't work. This adds a configuration to
openshift-tests to see if given the current proxy environment, we
would use a proxy to reach the API server. If so, then we skip
tests annotated with `[Skip:Proxy]`.
Comment on lines +102 to +106
url, _, err := rest.DefaultServerURL(clientConfig.Host, clientConfig.APIPath, schema.GroupVersion{}, false)
if err != nil {
return nil, err
}
state.APIURL = url
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@deads2k Needs a lgtm again. I had this logic reversed and it was causing a panic 🤦

@deads2k
Copy link
Contributor

deads2k commented Aug 23, 2021

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 23, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 23, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@stbenjam
Copy link
Member Author

/refresh

@stbenjam
Copy link
Member Author

The DNM labels seem to be stuck, any chance you can remove them @deads2k?

@stbenjam
Copy link
Member Author

stbenjam commented Sep 7, 2021

/hold

@stbenjam
Copy link
Member Author

stbenjam commented Sep 7, 2021

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 7, 2021
@stbenjam stbenjam changed the title test: skip tests that won't work behind a proxy automatically [WIP] test: skip tests that won't work behind a proxy automatically Sep 7, 2021
@stbenjam stbenjam changed the title [WIP] test: skip tests that won't work behind a proxy automatically test: skip tests that won't work behind a proxy automatically Sep 7, 2021
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 7, 2021
@stbenjam
Copy link
Member Author

stbenjam commented Sep 7, 2021

/retest

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 7, 2021

@stbenjam: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-metal-ipi-ovn-ipv6 6916835 link /test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@mandre
Copy link
Member

mandre commented Dec 3, 2021

/cherry-pick release-4.9

@openshift-cherrypick-robot

@mandre: new pull request created: #26664

Details

In response to this:

/cherry-pick release-4.9

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.

@andfasano
Copy link
Contributor

/cherry-pick release-4.8

@openshift-cherrypick-robot

@andfasano: #26398 failed to apply on top of branch "release-4.8":

Applying: test: skip tests that won't work behind a proxy automatically
Using index info to reconstruct a base tree...
M	test/extended/util/annotate/generated/zz_generated.annotations.go
M	test/extended/util/annotate/rules.go
M	test/extended/util/cluster/cluster.go
Falling back to patching base and 3-way merge...
Auto-merging test/extended/util/cluster/cluster.go
CONFLICT (content): Merge conflict in test/extended/util/cluster/cluster.go
Auto-merging test/extended/util/annotate/rules.go
CONFLICT (content): Merge conflict in test/extended/util/annotate/rules.go
Auto-merging test/extended/util/annotate/generated/zz_generated.annotations.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 test: skip tests that won't work behind a proxy automatically
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.8

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants