Flake ci-cluster-network-liveness and new backend disruption failures to avoid payload rejections #27990
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
… to avoid payload rejections
DennisPeriquet
changed the title
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DennisPeriquet, dgoodwin, xueqzhan 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 |
openshift-ci
bot
added
the
approved
|
@DennisPeriquet: 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. |
|
/retest-required |
| func isExcludedDisruptionBackend(name string) bool { | ||
| excludedNames := []string{ | ||
| "ci-cluster-network-liveness", | ||
| "kube-api-http1-external-lb", |
There was a problem hiding this comment.
It's a new backend, anything mentioning http is, the originals were left alone and are running along side these.
|
Job Failure Risk Analysis for sha: e244a5b |
openshift-merge-robot
merged commit 24350d6
into
openshift:master
TRT-1095
We'll flake these backends to avoid failing payloads.