Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-43745: Add support for IdleCloseTerminationPolicy #1178

Conversation

frobware
Copy link
Contributor

@frobware frobware commented Jan 10, 2025

This is #1166, but focuses on identifying flakes in Test_IdleConnectionTerminationPolicy. The goal of this PR is to run Test_IdleConnectionTerminationPolicy 30 times in isolation (with all other tests removed) to determine if it still flakes.

Enhanced response handlers (`/` and `/healthz`) to include
pod-specific headers (`x-pod-name` and `x-pod-namespace`).

Introduced new environment variables to control HTTP and HTTPS listeners:
- `HTTP2_TEST_SERVER_ENABLE_HTTP_LISTENER`: Enables/disables the HTTP listener.
- `HTTP2_TEST_SERVER_ENABLE_HTTPS_LISTENER`: Enables/disables the HTTPS listener.

Improved error handling to log and terminate if no listeners are
enabled, providing flexibility in determining which listeners to
activate.
Pickup openshift/api#2102

% git show 27316471eb72fe8fcf0d44fb5a0602f698f253dc
commit 27316471eb72fe8fcf0d44fb5a0602f698f253dc
Merge: de9de05a8 b7417509c
Author: openshift-merge-bot[bot] <148852131+openshift-merge-bot[bot]@users.noreply.github.com>
Date:   Wed Dec 18 10:31:50 2024 +0000

    Merge pull request #2102 from frobware/OCPBUGS-43745-idle-close-on-response

    OCPBUGS-43745: Add IdleCloseOnResponse field to IngressControllerSpec

Vendoring steps:

$ go mod edit -replace github.com/openshift/api=github.com/openshift/api@27316471eb72fe8fcf0d44fb5a0602f698f253dc
$ go mod tidy
$ go mod vendor
$ make update
Introduce logic in desiredRouterDeployment to set the environment
variable `ROUTER_IDLE_CLOSE_ON_RESPONSE` when the
`IdleConnectionTerminationPolicy` field in the IngressController spec is
set to `Deferred`. This change enables configuring HAProxy with the
`idle-close-on-response` option for better control over idle connection
termination behaviour.
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jan 10, 2025
@openshift-ci-robot
Copy link
Contributor

@frobware: This pull request references Jira Issue OCPBUGS-43745, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

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

In response to this:

This is similar to #1166, but focuses on identifying flakes in Test_IdleConnectionTerminationPolicy. The goal of this PR is to run Test_IdleConnectionTerminationPolicy 30 times in isolation (with all other tests removed) to determine if it still flakes.

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.

Copy link
Contributor

openshift-ci bot commented Jan 10, 2025

[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 frobware. For more information see the 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:

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

@frobware
Copy link
Contributor Author

/hold

@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 Jan 10, 2025
Copy link
Contributor

openshift-ci bot commented Jan 10, 2025

@frobware: 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-aws-gatewayapi 1d73e8a link false /test e2e-aws-gatewayapi
ci/prow/e2e-azure-ovn 1d73e8a link false /test e2e-azure-ovn
ci/prow/verify 1d73e8a link true /test verify
ci/prow/e2e-aws-operator 1d73e8a link true /test e2e-aws-operator
ci/prow/e2e-azure-operator 1d73e8a link true /test e2e-azure-operator
ci/prow/e2e-gcp-operator 1d73e8a link true /test e2e-gcp-operator
ci/prow/e2e-aws-operator-techpreview 1d73e8a link false /test e2e-aws-operator-techpreview

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

@frobware
Copy link
Contributor Author

Running Test_IdleConnectionTerminationPolicy didn't fail in:

22 matches for "^--- PASS: TestAll" in buffer: *p
67:--- PASS: TestAll (294.71s)
134:--- PASS: TestAll (314.21s)
200:--- PASS: TestAll (309.31s)
267:--- PASS: TestAll (281.41s)
334:--- PASS: TestAll (311.44s)
402:--- PASS: TestAll (314.11s)
470:--- PASS: TestAll (325.19s)
537:--- PASS: TestAll (309.79s)
605:--- PASS: TestAll (315.53s)
672:--- PASS: TestAll (310.43s)
739:--- PASS: TestAll (310.38s)
807:--- PASS: TestAll (325.37s)
876:--- PASS: TestAll (333.13s)
947:--- PASS: TestAll (346.14s)
1016:--- PASS: TestAll (334.22s)
1086:--- PASS: TestAll (305.35s)
1152:--- PASS: TestAll (308.38s)
1220:--- PASS: TestAll (293.24s)
1286:--- PASS: TestAll (313.13s)
1353:--- PASS: TestAll (397.70s)
1422:--- PASS: TestAll (334.06s)
1491:--- PASS: TestAll (335.01s)

Then the cluster expired.

@frobware frobware closed this Jan 13, 2025
@openshift-ci-robot
Copy link
Contributor

@frobware: This pull request references Jira Issue OCPBUGS-43745. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

This is #1166, but focuses on identifying flakes in Test_IdleConnectionTerminationPolicy. The goal of this PR is to run Test_IdleConnectionTerminationPolicy 30 times in isolation (with all other tests removed) to determine if it still flakes.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants