-
Notifications
You must be signed in to change notification settings - Fork 193
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
Retry ipset DestroySet/DestroyAllSets if error indicates in use #2978
Conversation
🤖 Created branch: z_pr2978/tpantelis/ipset_destroy |
This PR/issue depends on:
|
The unit test failure is unrelated to the changes in this PR. It was orthogonally introduced by the admiral bump and is addressed by submariner-io/admiral#891. |
66f311c
to
87e0072
Compare
...instead of the K8s exec wrapper as the former provides a fake implementation that is simpler and easer to use. Signed-off-by: Tom Pantelis <[email protected]>
This handles the case where a set is destroyed right after associated IP table rule(s) are deleted where the latter may not be complete yet. Retry up to 2 seconds. Fixes submariner-io#1746 Signed-off-by: Tom Pantelis <[email protected]>
Signed-off-by: Tom Pantelis <[email protected]>
87e0072
to
d170b91
Compare
🤖 Closed branches: [z_pr2978/tpantelis/ipset_destroy] |
This handles the case where a set is destroyed right after associated IP table rule(s) are deleted where the latter may not be complete yet. Retry up to 2 seconds.
Fixes #1746
Depends on submariner-io/admiral#886