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

Automated backport of #2399: Fix race when out-of-order RemoteEndpoint events are seen #2424

Commits on Apr 17, 2023

  1. Fix race when out-of-order RemoteEndpoint events are seen

    When there is a gateway migration in a remote cluster or if there
    is any stale endpoint on the Broker associated with the remoteCluster,
    the events might come in out of order which can create issues for
    datapath connectivity. The existing code was already having checks
    to ignore stale endpoint notifications in the kubeproxy and OVN handler.
    However, similar check was missing in MTU handler and an issue was
    seen in one of the environments. This PR moves the checks to the
    event handler framework and removes them from the registered handlers
    so that the fix will apply to all the handlers.
    
    Signed-off-by: Sridhar Gaddam <sgaddam@redhat.com>
    sridhargaddam authored and Jaanki committed Apr 17, 2023
    Configuration menu
    Copy the full SHA
    c585c19 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    9b55b29 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    4c7de3a View commit details
    Browse the repository at this point in the history