OCPBUGS-26440: feat: add buffer interval for SNO pathological events #28709
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
9399458
to
dad8e48
Compare
|
Job Failure Risk Analysis for sha: dad8e48
|
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
dad8e48
to
9a62f62
Compare
|
Job Failure Risk Analysis for sha: 9a62f62
|
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
9a62f62
to
cdbed6f
Compare
|
Job Failure Risk Analysis for sha: cdbed6f
|
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
cdbed6f
to
679f3e7
Compare
|
Job Failure Risk Analysis for sha: 679f3e7
|
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
679f3e7
to
26a2024
Compare
|
Job Failure Risk Analysis for sha: 26a2024
|
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
26a2024
to
0a3742d
Compare
|
Job Failure Risk Analysis for sha: 0a3742d
|
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
0a3742d
to
666cc31
Compare
eggfoobar
changed the title
openshift-ci-robot
added
jira/severity-critical
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
openshift-ci-robot
added
the
jira/valid-bug
|
@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
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
eggfoobar
changed the title
|
@eggfoobar: This pull request references Jira Issue OCPBUGS-26440, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
pkg/monitortestlibrary/pathologicaleventlibrary/duplicated_event_patterns.go
Show resolved
Hide resolved
|
/lgtm |
openshift-merge-robot
added
the
needs-rebase
openshift-ci
bot
added
the
approved
updated logic for disurption interval skip on SNO to look at the default namespace for the kuberentes service being down Signed-off-by: ehila <[email protected]>
eggfoobar
force-pushed
the
fix-sno-disruption
branch
from
666cc31
to
a4c77d3
Compare
openshift-merge-robot
removed
the
needs-rebase
|
/lgtm |
|
[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:
Approvers can indicate their approval by writing |
|
@eggfoobar: The following tests failed, say
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. |
openshift-merge-bot
bot
merged commit f9eeb48
into
openshift:master
|
@eggfoobar: Jira Issue OCPBUGS-26440: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-26440 has been moved to the MODIFIED state. In response to this:
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. |
|
[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. |
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.