-
Notifications
You must be signed in to change notification settings - Fork 348
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
Enable IPv6 e2e tests for control-plane #2276
Conversation
95b4a15
to
e15eed8
Compare
@aojea @danwinship can you PTAL at this PR and help to determine if these tests should be skipped, if the test needs updating, or if there is a bug that needs to be fixed? Thanks! |
@creydr added the failure reason for each of the tests in the description, we can merge this to have coverage and start to work in each failure, most probably is that most tests doesn't support ipv6 ... then is one Pr fixing one test and removing the skip |
Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
e15eed8
to
81e342a
Compare
/lgtm |
SDN-4930,OCPBUGS-38949: Downstream Merge 28th August
- What this PR does and why is it needed
This PR enables the e2e tests for IPv6 for the control-plane.
Currently not-IPv6-ready tests are excluded/skipped.
- Special notes for reviewers
A list of the skipped tests can be found at the end of this PR with failure messages and links to the failed CI jobs. This can be taken as a starting point to make the failed tests IPv6 ready and include them step by step in the test suite.
- How to verify it
The ovn-ci workflows include two new "steps" for control-plane IPv6 e2e tests (gateway-mode: local & shared).
- Description for the changelog
none
The following contains a list of the excluded and failing tests and a short info about the failure:
Test: Should be allowed by externalip services
Example for Failed CI run:
Test: should provide connection to external host by DNS name from a pod
Example for failed CI runs:
Test: should provide Internet connection continuously when master is killed
Example for failed CI runs:
Test: should provide Internet connection continuously when ovn-k8s pod is killed
Example for failed CI runs:
Test: Should validate connectivity from a pod to a non-node host address on same node
Example for failed CI runs:
Test: Should validate connectivity to an external gateway's loopback address via a pod with external gateway annotations
Example for failed CI runs:
Test: Should validate connectivity to multiple external gateways for an ECMP scenario
Example for failed CI runs:
Test: Should validate connectivity without vxlan before and after updating the namespace annotation to a new external gateway
Example for failed CI runs:
Test: Should validate ICMP connectivity to an external gateway's loopback address via a pod with external gateway annotations enabled
Example for failed CI runs:
Test: Should validate ICMP connectivity to multiple external gateways for an ECMP scenario
Example for failed CI runs:
Test: Should validate ingress connectivity from an external gateway
Example for failed CI runs:
Test: Should validate NetFlow data of br-int is sent to an external gateway
Example for failed CI runs:
Test: Should validate TCP/UDP connectivity to an external gateway's loopback address via a pod with external gateway annotations enabled
or
Example for failed CI runs:
BFD succeeds: 2896250600#step:11:3579
Test: Should validate TCP/UDP connectivity to multiple external gateways for a UDP / TCP scenario
Example for failed CI runs:
Succeeded in 2896285118#step:11:428
Test: Should validate the egress firewall policy functionality against remote hosts
Example for failed CI runs:
Test: Should validate the egress IP functionality against remote hosts
Example for failed CI runs:
Succeeded in 2896285118#step:11:1309
Test: recovering from deleting db files while maintain connectivity
Example for failed CI runs:
Succeeded in 2896285118#step:11:841