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

Continue to process cmdDel() in case of no network namespace #326

Merged
merged 1 commit into from
May 30, 2019

Conversation

s1061123
Copy link
Member

K8s with docker runtime, cmdDel() is invoked with empty network
namespace in case of restart node. Currently multus just returns
but CNI spec mention that we should invoke CNI plugin to cleanup.

This PR deletes "return nil" and proceeds to invoke CNI plugins
DEL. Fix #323.

K8s with docker runtime, cmdDel() is invoked with empty network
namespace in case of restart node. Currently multus just returns
but CNI spec mention that we should invoke CNI plugin to cleanup.

This PR deletes "return nil" and proceeds to invoke CNI plugins
DEL. Fix #323.
@s1061123 s1061123 requested a review from dougbtv May 30, 2019 05:37
@coveralls
Copy link

Pull Request Test Coverage Report for Build 778

  • 1 of 2 (50.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.05%) to 54.867%

Changes Missing Coverage Covered Lines Changed/Added Lines %
multus/multus.go 1 2 50.0%
Totals Coverage Status
Change from base Build 776: 0.05%
Covered Lines: 699
Relevant Lines: 1274

💛 - Coveralls

@dougbtv dougbtv added the release-v3 PRs to make it in release branch label May 30, 2019
@dougbtv dougbtv merged commit f00ac9b into master May 30, 2019
@s1061123 s1061123 deleted the fix/restart-node-1 branch June 14, 2019 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-v3 PRs to make it in release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Multus IP resource leakage after node reboot
3 participants