Skip to content

Bug 2071139: delete default ingress pod if it is scheduled where another router pod already is#720

Merged
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
deads2k:add-pod
Apr 1, 2022
Merged

Bug 2071139: delete default ingress pod if it is scheduled where another router pod already is#720
openshift-merge-robot merged 2 commits intoopenshift:masterfrom
deads2k:add-pod

Conversation

@deads2k
Copy link
Contributor

@deads2k deads2k commented Mar 14, 2022

Anti-affinity in the scheduler has a bug and isn't properly spreading pods. This fits a new library-go controller into the ingress-operator to delete a mal-scheduled pod. If it finds two non-deleted pods using the selector on the same node, then the oldest pod is deleted. Oldest is chosen so that a deployment controller could still make progress. This different that is commonly done to preserve the oldest to disrupt the fewest connections, but it's better to avoid blocking the deployment controller.

I chose to start with ingress because it has the biggest multiplier and this doesn't fully resolve the bug for this component, it only impacts the default ingress.

/hold
This PR is proof for openshift/library-go#1330

@deads2k
Copy link
Contributor Author

deads2k commented Mar 14, 2022

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 14, 2022
@openshift-ci openshift-ci bot requested review from candita and rfredette March 14, 2022 18:14
@deads2k deads2k force-pushed the add-pod branch 2 times, most recently from 4e3a09a to 2779ca2 Compare March 16, 2022 19:02
@deads2k
Copy link
Contributor Author

deads2k commented Mar 24, 2022

/test all

@deads2k
Copy link
Contributor Author

deads2k commented Mar 31, 2022

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Mar 31, 2022

/hold cancel

The controller and unit tests merged to library-go, so this bump is now real.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 31, 2022
@deads2k
Copy link
Contributor Author

deads2k commented Mar 31, 2022

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Mar 31, 2022

    "Operator \"cluster-monitoring-operator\" produces more watch requests than expected: watchrequestcount=104, upperbound=96, ratio=1.0833333333333333",

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Mar 31, 2022

/retest

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 1, 2022
@deads2k
Copy link
Contributor Author

deads2k commented Apr 1, 2022

Fix here openshift/library-go#1344, will pick when it lands.

@deads2k
Copy link
Contributor Author

deads2k commented Apr 1, 2022

bumped

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 1, 2022
@Miciah
Copy link
Contributor

Miciah commented Apr 1, 2022

Thanks!
/lgtm

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

openshift-ci bot commented Apr 1, 2022

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Apr 1, 2022
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 1, 2022

@deads2k: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@Miciah
Copy link
Contributor

Miciah commented Apr 1, 2022

/retitle Bug 2071139: delete default ingress pod if it is scheduled where another router pod already is

@openshift-ci openshift-ci bot changed the title delete default ingress pod if it is scheduled where another router pod already is Bug 2071139: delete default ingress pod if it is scheduled where another router pod already is Apr 1, 2022
@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 Apr 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 1, 2022

@deads2k: This pull request references Bugzilla bug 2071139, 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)

Requesting review from QA contact:
/cc @lihongan

Details

In response to this:

Bug 2071139: delete default ingress pod if it is scheduled where another router pod already is

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 a review from lihongan April 1, 2022 23:43
@openshift-merge-robot openshift-merge-robot merged commit 39b074e into openshift:master Apr 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 1, 2022

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

Bugzilla bug 2071139 has been moved to the MODIFIED state.

Details

In response to this:

Bug 2071139: delete default ingress pod if it is scheduled where another router pod already is

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.

4 participants