-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Azure: Add netplan driver filter when using hv_netvsc driver #539
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have logs for this? There should not be two hv_netvsc interfaces with the same mac; for advanced networking, the kernel bonds an SR_IOV device (which previously was an mxl4_core device, and DatasourceAzure blacklists any interfaces using this driver, so we ignore any physical interfaces that driver).
It's possible there is a different driver doing SRIOV so we're not properly masking out the duplicate mac interface that's really the SRIOV device.
I notice the bug this fixes doesn't have any follow up there w.r.t the logs they posted. It'd be good to update that with:
from a failing instance to confirm the premise of this fix.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I think this is the right fix; I think we overlooked preventing network-v2 config from matching non-hyperv nics once we started crawling IMDS; It's possible that this was not noticed as there is a race between the kernel completes the SRIOV bond and when cloud-init starts to generate networking.
Let's confirm that IMDS does not include an SRIOV device (I don't think it will since it contains a duplicate mac of one of the hyperv nics).
For fallback, we need to update the blacklist to include mlx5-core (newer hardware). This is only important for Xenial (and non-netplan rendered targets) I believe those paths will ignore the mlx devices, but we should also ensure that the driver value is emitted in the udev rule (