OCPBUGS-26440: feat: add buffer interval for SNO pathological events

[eggfoobar]

during single node deployments knowing the window between graceful shutdown end and readyz start is helpful to determine when connection refused events are expected. This update makes use of a generated buffer interval between the time the graceful shutdown signal is received and some specified buffer of time to account for the API server coming back up.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: dad8e48494b46e594e22e1c04e27a483534dfdff

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-fips	IncompleteTests Tests for this run (98) are below the historical average (1576): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 9a62f628b625358d50e92147126845e9c5a16db2

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-fips	IncompleteTests Tests for this run (98) are below the historical average (1517): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt-bot]

Job Failure Risk Analysis for sha: cdbed6f5da4a5aa4389d1991b3e1af4880fc1689

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (13) are below the historical average (915): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade	IncompleteTests Tests for this run (17) are below the historical average (752): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-gcp-csi	IncompleteTests Tests for this run (16) are below the historical average (685): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-aws-ovn-fips	IncompleteTests Tests for this run (16) are below the historical average (1334): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 679f3e77dba801f98fc8887f5ba509eb3c9127c0

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (98) are below the historical average (924): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade	IncompleteTests Tests for this run (100) are below the historical average (702): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 26a2024e69387f7a77e2974559853ea8d6d73431

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (13) are below the historical average (1109): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 0a3742d04ec63a4e2015a3646691feb4bb1ca0c1

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (99) are below the historical average (1165): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-ci-robot]

@eggfoobar: This pull request references Jira Issue OCPBUGS-26440, 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.16.0) matches configured target version for branch (4.16.0) * bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @wangke19

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

In response to [this](https://github.com/openshift/origin/pull/28709): >during single node deployments knowing the window between graceful shutdown end and readyz start is helpful to determine when connection refused events are expected. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@eggfoobar: This pull request references Jira Issue OCPBUGS-26440, 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 @wangke19

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

In response to [this](https://github.com/openshift/origin/pull/28709): >during single node deployments knowing the window between graceful shutdown end and readyz start is helpful to determine when connection refused events are expected. This update makes use of a generated buffer interval between the time the graceful shutdown signal is received and some specified buffer of time to account for the API server coming back up. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[neisw]

/lgtm

[neisw]

/lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eggfoobar, neisw

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/origin/blob/master/OWNERS)~~ [neisw] 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]

/retest-required

Remaining retests: 0 against base HEAD 221cc8800f27f22dadb63f009ee93dfda9992f88 and 2 for PR HEAD a4c77d3a739023e28b7e7b31d05a7004638e5f87 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 07e13e2b5fa321060bbaaa787b38302620e8f1a3 and 1 for PR HEAD a4c77d3a739023e28b7e7b31d05a7004638e5f87 in total

[openshift-ci[bot]]

@eggfoobar: 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-csi	a4c77d3a739023e28b7e7b31d05a7004638e5f87	link	false	/test e2e-gcp-csi
ci/prow/e2e-aws-ovn-single-node-serial	a4c77d3a739023e28b7e7b31d05a7004638e5f87	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-rt-upgrade	a4c77d3a739023e28b7e7b31d05a7004638e5f87	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-ovn-single-node-upgrade	a4c77d3a739023e28b7e7b31d05a7004638e5f87	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node	a4c77d3a739023e28b7e7b31d05a7004638e5f87	link	false	/test e2e-aws-ovn-single-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

@eggfoobar: Jira Issue OCPBUGS-26440: All pull requests linked via external trackers have merged:

• openshift/kubernetes#1914
• openshift/origin#28709

Jira Issue OCPBUGS-26440 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/origin/pull/28709): >during single node deployments knowing the window between graceful shutdown end and readyz start is helpful to determine when connection refused events are expected. This update makes use of a generated buffer interval between the time the graceful shutdown signal is received and some specified buffer of time to account for the API server coming back up. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202405010518.p0.gf9eeb48.assembly.stream.el9 for distgit openshift-enterprise-tests. All builds following this will include this PR.