-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Ignore down interfaces when calculating host MTU. #8496
Conversation
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.
Looking good! Just one comment.
felix/fv/mtu_test.go
Outdated
EventuallyWithOffset(1, func() string { | ||
out, _ := felix.ExecOutput("cat", "/var/lib/calico/mtu") | ||
return out | ||
}, "60s", "500ms").Should(ContainSubstring(fmt.Sprintf("%d", mtu))) |
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.
Does ContainSubstring
succeed if output is 13508
but the correct value of mtu should be 1350
?
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.
Feels unlikely but trivial to fix so why not.
8e43314
to
4a17767
Compare
/merge-when-ready squash-commits |
OK, I will merge the pull request when it's ready, squash the commits when I merge it, and leave the branch after I've merged it. |
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.
LGTM
Description
Ignore interfaces that are down when auto-detecting MTU.
Related issues/PRs
CORE-10150
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Host MTUEvery PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.