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

Bug 2092961: Flake almost all ci cluster to external svc disruption. #27210

Merged
merged 1 commit into from Jun 4, 2022

Conversation

dgoodwin
Copy link
Contributor

@dgoodwin dgoodwin commented Jun 3, 2022

Recently merged this backend and we're already seeing disruption to the
external service that doesn't even correlate to observed disruption of
the cluster under test.

Allowing 10 minutes of disruption means we'll almost always flake
instead of fail, while we gather more data and try to understand what's
happening.

Recently merged this backend and we're already seeing disruption to the
external service that doesn't even correlate to observed disruption of
the cluster under test.

Allowing 10 minutes of disruption means we'll almost always flake
instead of fail, while we gather more data and try to understand what's
happening.
@dgoodwin dgoodwin changed the title Flake almost all ci cluster to external svc disruption. Bug 2092961: Flake almost all ci cluster to external svc disruption. Jun 3, 2022
@dgoodwin
Copy link
Contributor Author

dgoodwin commented Jun 3, 2022

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jun 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 3, 2022

@dgoodwin: This pull request references Bugzilla bug 2092961, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

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

In response to this:

Bug 2092961: Flake almost all ci cluster to external svc disruption.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 3, 2022

@dgoodwin: This pull request references Bugzilla bug 2092961, which is valid.

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

In response to this:

/bugzilla 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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot requested review from deads2k and mrogers950 June 3, 2022 14:21
@deads2k
Copy link
Contributor

deads2k commented Jun 3, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 3, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, dgoodwin

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2022
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 2 against base HEAD de85561 and 8 for PR HEAD 7569452 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2022

@dgoodwin: 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-agnostic-cmd 7569452 link false /test e2e-agnostic-cmd
ci/prow/e2e-metal-ipi-ovn-ipv6 7569452 link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-single-node-upgrade 7569452 link false /test e2e-aws-single-node-upgrade
ci/prow/e2e-aws-single-node 7569452 link false /test e2e-aws-single-node
ci/prow/e2e-gcp-ovn-rt-upgrade 7569452 link false /test e2e-gcp-ovn-rt-upgrade

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-robot openshift-merge-robot merged commit b9e505e into openshift:master Jun 4, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2022

@dgoodwin: All pull requests linked via external trackers have merged:

Bugzilla bug 2092961 has been moved to the MODIFIED state.

In response to this:

Bug 2092961: Flake almost all ci cluster to external svc disruption.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants