You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pchaigno opened this issue
Jan 19, 2021
· 1 comment
· Fixed by #15959
Assignees
Labels
area/CIContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!pinnedThese issues are not marked stale by our issue bot.
The fragment tracking test is currently failing on GKE, with zero fragments received at the destination. The issue can be easily reproduced by enabling test Supports IPv4 fragments on GKE.
The text was updated successfully, but these errors were encountered:
pchaigno
added
area/CI
Continuous Integration testing issue or flake
ci/flake
This is a known failure that occurs in the tree. Please investigate me!
labels
Jan 19, 2021
I'm hitting the same error if I run the test on Packet nodes with per-endpoint routes enabled by default:
Failed to account for IPv4 fragments to 10.97.69.6 (in)
Expected
<[]int | len:2, cap:2>: [0, 8]
To satisfy at least one of these matchers: [%!s(*matchers.EqualMatcher=&{[0 4]}) %!s(*matchers.EqualMatcher=&{[4 0]})]
I suspect both are the same issue with per-endpoint routes as the common cause (they are enabled by default on GKE).
Updating the title accordingly.
pchaigno
changed the title
CI: GKE: K8sServicesTest Checks service across nodes Supports IPv4 fragments
CI: K8sServicesTest Checks service across nodes Supports IPv4 fragments failing with endpoint routes enabled
Feb 22, 2021
area/CIContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!pinnedThese issues are not marked stale by our issue bot.
The fragment tracking test is currently failing on GKE, with zero fragments received at the destination. The issue can be easily reproduced by enabling test
Supports IPv4 fragments
on GKE.Related: #14639
The text was updated successfully, but these errors were encountered: