OCPBUGS-63686: OVN EIP: improve startup syncer for EIP#2839
OCPBUGS-63686: OVN EIP: improve startup syncer for EIP#2839jluhrsen wants to merge 4 commits intoopenshift:release-4.20from
Conversation
…odes Previously, we were checking if the next hop IP is valid for the current set of nodes but we werent but every EgressIP is assigned to a subset of the total nodes. Stale LRPs could occur if a node hosted eip pods, ovnkube-controller is down, and the EIP moved to a new Node which said controller is down. Signed-off-by: Martin Kennelly <mkennell@redhat.com> Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
For IC mode, there is no expectation we can fetch a remote nodes LSP, therefore, by skipping (continue), it is causing us to skip generating valid next hops for the remote node. Later in sync LRPs, when a valid next hop is inspected, we do not find it valid and remove that valid next hop. Handlers will re-add it shortly later. Signed-off-by: Martin Kennelly <mkennell@redhat.com>
Signed-off-by: Martin Kennelly <mkennell@redhat.com>
Previous to this change, we dont emit log error for stale next hops. Signed-off-by: Martin Kennelly <mkennell@redhat.com>
openshift-ci-robot
added
jira/severity-critical
|
@jluhrsen: This pull request references Jira Issue OCPBUGS-63686, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/payload 4.20 ci nightly |
|
@jluhrsen: An error was encountered. No known errors were detected, please see the full error message for details. Full error message.
could not resolve jobs for 4.20 ci nightly: job type is not supported: nightly
Please contact an administrator to resolve this issue. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jluhrsen The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/jira refresh |
|
@jluhrsen: This pull request references Jira Issue OCPBUGS-63686, which is invalid:
Comment DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@jluhrsen: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/payload 4.20 ci blocking |
|
@jluhrsen: trigger 5 job(s) of type blocking for the ci release of OCP 4.20
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/59ce3b40-b61d-11f0-8530-44f1d5671e58-0 trigger 13 job(s) of type blocking for the nightly release of OCP 4.20
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/59ce3b40-b61d-11f0-8530-44f1d5671e58-1 |
|
@pperiyasamy , payloads are good: /payload-job periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade |
|
@jluhrsen: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/80ee0100-b691-11f0-9a0e-1f2c1c23cb06-0 |
|
this is included in #2835 |
|
@jluhrsen: Closed this PR. DetailsIn response to this:
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-sigs/prow repository. |
|
@jluhrsen: This pull request references Jira Issue OCPBUGS-63686. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
3 participants
this a manual cherry-pick of this upstream PR which landed in this d/s merge