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

f5 node watch fix - needs a cache to process 'MODIFY' events #11742

Merged
merged 1 commit into from Nov 3, 2016

Conversation

rajatchopra
Copy link
Contributor

Poor code before, never accounted that nodes that were already created before F5 is launched will only get a MODIFIED event. This code takes care of that (and ignores the subsequent MODIFY events caused by status updates).

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1389706

@pravisankar Please review. Thanks for the hint.
cc @openshift/networking

@dcbw
Copy link
Contributor

dcbw commented Nov 2, 2016

LGTM

@rajatchopra
Copy link
Contributor Author

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 315c2e4

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11032/) (Base Commit: 2583f1e)

Copy link

@pravisankar pravisankar left a comment

Choose a reason for hiding this comment

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

LGTM

@pravisankar
Copy link

[merge]

1 similar comment
@eparis
Copy link
Member

eparis commented Nov 3, 2016

[merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented Nov 3, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11032/) (Image: devenv-rhel7_5306)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 315c2e4

@openshift-bot openshift-bot merged commit 3b6c372 into openshift:master Nov 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants