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 1982766: [on-prem] Make ingress VIP more tolerant to failures #2679

Merged
merged 1 commit into from Jul 28, 2021

Conversation

mandre
Copy link
Member

@mandre mandre commented Jul 19, 2021

We've noticed that the ingress VIP could be flapping in some
environments where the keepalived check fails due to timeout. We should
make the ingress check more resilient to errors and start using fall
and raise to mitigate flapping as we did for the API checks.

We've noticed that the ingress VIP could be flapping in some
environments where the keepalived check fails due to timeout. We should
make the ingress check more resilient to errors and start using `fall`
and `raise` to mitigate flapping as we did for the API checks.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 19, 2021

@mandre: This pull request references Bugzilla bug 1982766, 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.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @eurijon

In response to this:

Bug 1982766: [on-prem] Make ingress VIP more tolerant to failures

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 added bugzilla/severity-high Referenced Bugzilla bug's severity is high 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 Jul 19, 2021
@mandre
Copy link
Member Author

mandre commented Jul 19, 2021

/cc @cybertron @yboaron
It seems like a sensible thing to add fall and raise directives to the ingress checks like we do on the API check and I was wondering if this was something that has previously been discussed and discarded or just an overlook. Reviews welcome :)

@openshift-ci openshift-ci bot requested review from cybertron and yboaron July 19, 2021 11:50
@cybertron
Copy link
Member

/lgtm

Agreed, this seems quite reasonable.

/test e2e-openstack
/test e2e-ovirt
/test e2e-vsphere
/cc @Gal-Zaidman @jcpowermac @patrickdillon

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 21, 2021
@mandre
Copy link
Member Author

mandre commented Jul 22, 2021

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 22, 2021

@mandre: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-workers-rhel7 881f3b0 link /test e2e-aws-workers-rhel7
ci/prow/e2e-aws-techpreview-featuregate 881f3b0 link /test e2e-aws-techpreview-featuregate
ci/prow/e2e-aws-single-node 881f3b0 link /test e2e-aws-single-node
ci/prow/e2e-ovn-step-registry 881f3b0 link /test e2e-ovn-step-registry
ci/prow/e2e-aws-disruptive 881f3b0 link /test e2e-aws-disruptive

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.

@jcpowermac
Copy link
Contributor

/lgtm

@mandre
Copy link
Member Author

mandre commented Jul 28, 2021

As the bot suggests.
/assign sinnykumari

All relevant jobs are passing, PTAL.

Copy link
Contributor

@sinnykumari sinnykumari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All relevant tests are passing.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 28, 2021
@Gal-Zaidman
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 28, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cybertron, Gal-Zaidman, jcpowermac, mandre, sinnykumari

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-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 4ad850b into openshift:master Jul 28, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 28, 2021

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

Bugzilla bug 1982766 has been moved to the MODIFIED state.

In response to this:

Bug 1982766: [on-prem] Make ingress VIP more tolerant to failures

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-high Referenced Bugzilla bug's severity is high 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

7 participants