OCPBUGS-62232: Set -fin timeouts in HAProxy config

[cybertron]

We have a bug where misbehaved clients are exhausting the connection limits by starting a connection and abandoning it before it is even established. Setting the client-fin timeout is a recommended option to address this sort of situation. This patch also sets server-fin in the interest of symmetry and avoiding any similar issues on the server side.

- What I did

- How to verify it

- Description for the changelog

[openshift-ci-robot]

@cybertron: This pull request references Jira Issue OCPBUGS-62232, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

We have a bug where misbehaved clients are exhausting the connection limits by starting a connection and abandoning it before it is even established. Setting the client-fin timeout is a recommended option to address this sort of situation. This patch also sets server-fin in the interest of symmetry and avoiding any similar issues on the server side.

- What I did

- How to verify it

- Description for the changelog

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: cybertron
Once this PR has been reviewed and has the lgtm label, please assign pablintino for approval. 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:

• 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]

@cybertron: 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-azure-ovn-upgrade-out-of-change	a55feb4	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-aws-ovn	a55feb4	link	true	/test e2e-aws-ovn
ci/prow/bootstrap-unit	a55feb4	link	false	/test bootstrap-unit
ci/prow/e2e-aws-mco-disruptive	a55feb4	link	false	/test e2e-aws-mco-disruptive
ci/prow/okd-scos-e2e-aws-ovn	a55feb4	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-agent-compact-ipv4	a55feb4	link	false	/test e2e-agent-compact-ipv4
ci/prow/e2e-gcp-mco-disruptive	a55feb4	link	false	/test e2e-gcp-mco-disruptive
ci/prow/e2e-gcp-op-ocl	a55feb4	link	false	/test e2e-gcp-op-ocl
ci/prow/e2e-aws-ovn-windows	a55feb4	link	false	/test e2e-aws-ovn-windows
ci/prow/e2e-openstack	a55feb4	link	false	/test e2e-openstack

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.

[cybertron]

/jira refresh

[openshift-ci-robot]

@cybertron: This pull request references Jira Issue OCPBUGS-62232, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

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

Requesting review from QA contact:
/cc @rbbratta

In response to this:

/jira refresh

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.