-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix up destination MAC of auto-egress-ip packets #17099
Fix up destination MAC of auto-egress-ip packets #17099
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.
Sweet! The change looks good to me. Glad you found the cause!
/lgtm
/approve
/kind bug |
/retest |
oops, it's actually broken |
Also, one final OVS flow fix for egress IPs
7862726
to
286af89
Compare
@knobunc had to tweak it to not try to read the actual tun0 MAC address from unit tests |
added another fix, for https://bugzilla.redhat.com/show_bug.cgi?id=1507871 |
/retest |
2 similar comments
/retest |
/retest |
/retest Flaked on #17105 |
/retest Flaked on #17105 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, eparis, knobunc The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue. |
Auto egress packets from pods on nodes other than the one with the egress IP were getting dropped. This turns out to be because the packets will be ignored if you output them on tun0 but they don't have tun0's MAC address as the destination MAC. (For local pods, the default route is via tun0, so the MAC is correct, but for remote pods, the default route is via the tun0 on their node, so the MAC was wrong for the node it eventually ended up on.)
Also includes two other auto-egress-ip OVS flow fixes.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1501876
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1507871