host-device: Bring interfaces up after moving into container #679
Conversation
This file contains 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
|
Your test failed, can you look into it @dpward ? |
|
@mccv1r0 Sorry for the delay. This should now bring the device back to its previous up/down state after a failure when moving it from container back to host. |
|
@dpward can you run gofmt on the hostdevice.go plugin? |
If an interface is not configured with IPAM (because it functions at layer 2), it will not be brought up otherwise. Signed-off-by: David Ward <[email protected]>
Signed-off-by: Casey Callendrello <[email protected]>
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.
If an interface is not configured with IPAM (because it functions at layer 2), it will not be brought up otherwise.
Fixes: #184