OCPBUGS-14914: e2e - test tunnel and server timeouts

[alebedev87]

This PR adds two tests to the e2e suite. They verify the behavior of the server and tunnel router timeouts. The following behaviors are supposed to be covered :

• server and tunnel timeouts set in the ingresscontroller's tunningOptions
• server and tunnel timeouts set in the route via the corresponding annotations
• difference between the default (ingresscontroller level) and the route level timeouts, including the changes made in OCPBUGS-14914: Set tunnel and server timeouts only at the backend level  router#536

A new test command is added to cluster-ingress-operator: serve-ws-test-server. It aims at imitating a WebSocket server similar to the other server commands: serve-grpc-test-server, serve-http2-test-server.

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-14914, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ShudiLi

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This PR adds two tests to the e2e suite. They test the 2 router timeouts which were modified by openshift/router#536: tunnel and server.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from alebedev87. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

@alebedev87: An error was encountered querying GitHub for users with public email ([email protected]) for bug OCPBUGS-14914 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message.

Post "http://ghproxy/graphql": dial tcp 172.30.229.2:80: connect: connection refused

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This PR adds two tests to the e2e suite. They test two router timeouts which were modified by openshift/router#536: tunnel and server.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-14914, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ShudiLi

In response to this:

This PR adds two tests to the e2e suite. They test two router timeouts: server and tunnel. They are supposed to cover the following behaviors:

• server and tunnel timeouts set in the ingresscontroller's tunningOptions
• server and tunnel timeouts set in the route via the corresponding annotations
• difference between the default (ingresscontroller level) and the route level timeouts, including the changes made in OCPBUGS-14914: Set tunnel and server timeouts only at the backend level  router#536

A new test command is added to cluster-ingress-operator: serve-ws-test-server. It aims at imitating a WebSocket server similar to the other server commands: serve-grpc-test-server, serve-http2-test-server.

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 openshift-eng/jira-lifecycle-plugin repository.

[ShudiLi]

/label qe-approved

[openshift-ci]

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

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-operator	4233b19	link	true	/test e2e-gcp-operator
ci/prow/e2e-azure-operator	4233b19	link	true	/test e2e-azure-operator
ci/prow/e2e-aws-operator	4233b19	link	true	/test e2e-aws-operator

Full PR test history. Your PR dashboard.

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.

[alebedev87]

/hold

Until openshift/router#536 is merged.

[Miciah]

/assign

[candita]

/assign

[candita]

E2E for TestTunnelTimeout never finds the host. May need to wait longer.

NAME TestAll/parallel/TestTunnelTimeout
operator_test.go:3344: lookup slow-wssrv-openshift-ingress.test-tunnel-timeout.ci-op-c3sylg6j-43abb.origin-ci-int-aws.dev.rhcloud.com on 172.30.0.10:53: no such host