-
Notifications
You must be signed in to change notification settings - Fork 333
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
Unskip ETP=local+terminating endpoints #4253
Conversation
✅ Deploy Preview for subtle-torrone-bb0c84 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
:P seems like we have regressed? |
test/scripts/e2e-kind.sh
Outdated
@@ -125,9 +125,6 @@ if [ "$DUALSTACK_CONVERSION" == true ]; then | |||
fi | |||
|
|||
if [ "$OVN_GATEWAY_MODE" == "local" ]; then | |||
if [ "$SKIPPED_TESTS" != "" ]; then | |||
SKIPPED_TESTS+="|" | |||
fi | |||
SKIPPED_TESTS+="should fallback to local terminating endpoints when there are no ready endpoints with externalTrafficPolicy=Local" |
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.
the other tests seem to have a newline that starts them, then groomTestList substitutes the newline for a |
Doesnt this need a newline as well?
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.
speaking of which @ricky-rav I should not have to skip this test anymore right? don't we support terminating endpoints feature with ETP=local?
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.
@trozet FYI in lgw v6 lane:
ginkgo --nodes=10 '--focus=\[Conformance\]|\[sig-network\]' '--skip=\[Feature:Networking-Performance\]|\[Feature:PerformanceDNS\]|Disruptive|DisruptionController|\[sig-apps\]\sCronJob|\[sig-storage\]|\[Feature:Federation\]|should\shave\sipv4\sand\sipv6\sinternal\snode\sip|kube-proxy|should\sset\sTCP\sCLOSE_WAIT\stimeout|named\sport.+\[Feature:NetworkPolicy\]|should\screate\sa\sPod\swith\sSCTP\sHostPort|service.kubernetes.io/headless|should\sresolve\sconnection\sreset\sissue\s#74839|sig-api-machinery|\[Feature:NoSNAT\]|LoadBalancers\sshould|configMap\snameserver|ClusterDns\s\[Feature:Example\]|should\sset\sdefault\svalue\son\snew\sIngressClass|should\sprevent\sIngress\screation\sif\smore\sthan\s1\sIngressClass\smarked\sas\sdefault|validates\sthat\sthere\sis\sno\sconflict\sbetween\spods\swith\ssame\shostPort\sbut\sdifferent\shostIP\sand\sprotocol|\[Feature:Networking-IPv6\]|should\sprovider\sInternet\sconnection\sfor\scontainers\susing\sDNS|\[Feature:Networking-IPv4\]|IPBlock.CIDR\sand\sIPBlock.Except|Network.+should\sresolve\sconnection\sreset\sissue|NetworkPolicy.+should\sallow\segress\saccess\sto\sserver\sin\sCIDR\sblock|\[Feature:.*DualStack.*\]|should\sfallback\sto\slocal\sterminating\sendpoints\swhen\sthere\sare\sno\sready\sendpoints\swith\sexternalTrafficPolicy=Local|\[Serial\]'
so I see the pipe getting added before the should fallback so we are good there I think ^ ?
[Feature:.*DualStack.*\]|should\sfallback\sto\slocal\sterminating\sendpoints\swhen\sthere\sare\sno\sready\sendpoints\swith\sexternalTrafficPolicy=Local|\[Serial\]'
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.
speaking of which @ricky-rav I should not have to skip this test anymore right? don't we support terminating endpoints feature with ETP=local?
Looking at the title of the test, I was going to say that we should wait for this PR of mine #4170 to be merged.
But then I ran the test on KIND both on the PR image and the master image. It works in both cases. :-o
So I looked at the test case and it's quite bizarre: it tests a terminating endpoint for a service with ETP=local, but the clients from which it connects to the service are all WITHIN the cluster, so ETP=local means nothing since we're not generating any external traffic and that's why my current fix isn't needed for this test after all.
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/service.go#L3043
In the upcoming weeks I should probably write a proper e2e test for this, possibly with Antonio's cloud load balancer for KIND.
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.
aha! so I guess I can remove skipping this then!
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.
yeah, let's remove 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.
done! let's see if it passes on v4 and v6 lanes correctly.
thank you for looking. |
Looking into the failures but its time boxed to today. |
also saving link here for @martinkennelly : https://github.com/ovn-org/ovn-kubernetes/actions/runs/8551587549/job/23431934438?pr=4253 rerunning that lane to ensure it was not flake, |
the |
be161f7
to
4db3d43
Compare
@ricky-rav PTAL |
4db3d43
to
293f54b
Compare
unrelated flakes: |
I think there are still tests that somehow we don't run in IPv6, but we do in IPv4 and dual-stack. In particular I found a bunch (#4170 (comment)) that only failed when tested in the one IPv6 CI lane we have downstream. I'll investigate further once I'm done with the 4.12 backport for that same PR. |
@ricky-rav yeah that's fine, the goal of this PR is to remove the skip we have currently which you mentioned is no longer needed right? or am I missing something? (note I don't intend to unskip all here) also there is a bunch of issues that we skip for v6 in general |
Signed-off-by: Surya Seetharaman <suryaseetharaman.9@gmail.com>
293f54b
to
b7d827a
Compare
Changes unknown |
UPDATE:
Original fix here went into #4256
I am converting this PR to fix: #4253 (comment)
OUTDATED INFO ON OLD PR:
I think we should definitely spend some time fixing #4229
cc @jluhrsen this might be why you saw some lanes not running tests and finishing in 5mins?
- What this PR does and why is it needed
Accidental addition of
|
pipe during skipping makes it||
which matches empty string which skips all tests :/Not on all lanes I think shard, local, v6 ones only:
- Special notes for reviewers
- How to verify it
- Description for the changelog