Skip to content

WIP: Set goaway-chance to .001 #1842

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sdodson
Copy link
Member

@sdodson sdodson commented May 14, 2025

Just to run disruption tests, once we know if this causes disruption test issues we'll fix those, by ensuring goaways are ignored, and be back to land this in a manner that sets the value to .001 for HA clusters and 0 non HA control planes.

Just to run disruption tests, once we know if this causes disruption test
issues we'll fix those, by ensuring goaways are ignored, and be back to
land this in a manner that sets the value to .001 for HA clusters and 0
non HA control planes.
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 14, 2025
Copy link
Contributor

openshift-ci bot commented May 14, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented May 14, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sdodson
Once this PR has been reviewed and has the lgtm label, please assign sanchezl 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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdodson
Copy link
Member Author

sdodson commented May 14, 2025

/aggregate-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips 2

@sdodson
Copy link
Member Author

sdodson commented May 15, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips 5

Copy link
Contributor

openshift-ci bot commented May 15, 2025

@sdodson: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fa423af0-3129-11f0-8d98-970326552fbd-0

@sdodson
Copy link
Member Author

sdodson commented May 15, 2025

/aggregate-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips 2

@sdodson
Copy link
Member Author

sdodson commented May 15, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips 5

Copy link
Contributor

openshift-ci bot commented May 15, 2025

@sdodson: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/826bf7b0-31b9-11f0-991e-e28535f9c0fc-0

@sdodson
Copy link
Member Author

sdodson commented May 16, 2025

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips 5

But no reported signs of disruption in api server observed, lets try some more.

Copy link
Contributor

openshift-ci bot commented May 16, 2025

@sdodson: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/723f6860-3261-11f0-879d-3840f04ef5c0-0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant