Delete vlan default GW interface #1175
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Del command cleans up default vlan interface Signed-off-by: Marcelo <[email protected]>
|
It makes sense that we should be clearing up the host-side interface, but (as we discussed synchronously), what happens if there's a delayed DEL that collides with an existing container? Is there a chance we could take another container offline? Is there an easy way to tell if the host-side vlan interfaces is still "owned" by the container being deleted (veth peer perhaps?) |
|
Yes, it's not safe. I'll explore some options. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Del command cleans up default vlan interface