Bug 1973995

+++ This bug was initially created as a clone of Bug #1972684 +++

Description of problem:
[sig-network] [Feature:IPv6DualStack] [LinuxOnly] should have ipv4 and ipv6 node podCIDRs
[sig-network] [Feature:IPv6DualStack] [LinuxOnly] Granular Checks: Services Secondary IP Family should function for client IP based session affinity: http
[sig-network] [Feature:IPv6DualStack] [LinuxOnly] Granular Checks: Services Secondary IP Family should function for client IP based session affinity: udp

These 3 tests are permanently failing in e2e-metal-ipi-ovn-dualstack jobs.

Version-Release number of selected component (if applicable):
4.8+

How reproducible:
Run e2e-metal-ipi-ovn-dualstack CI job.

Actual results:
Tests are failing

Expected results:
Tests pass

Additional info:

https://testgrid.k8s.io/redhat-openshift-ocp-release-4.8-informing#periodic-ci-openshift-release-master-nightly-4.8-e2e-metal-ipi-ovn-dualstack

--- Additional comment from aguclu on 2021-06-16 13:57:11 UTC ---

[sig-network] [Feature:IPv6DualStack] [LinuxOnly] should have ipv4 and ipv6 node podCIDRs test is failing in here https://github.com/openshift/origin/blob/b6793727bc9cfaaf6b3320af053d3495dccd896c/vendor/k8s.io/kubernetes/test/e2e/network/dual_stack.go#L77 because it expects podCIDRs returns 2 values, but function returns 0.

After checking from the must-gather logs, nodes have no podCIDRs. And according to here https://github.com/openshift/origin/blob/b6793727bc9cfaaf6b3320af053d3495dccd896c/vendor/k8s.io/api/core/v1/types.go#L4600, this field is optional. It seems like a bug in upstream test.

--- Additional comment from aguclu on 2021-06-16 14:09:49 UTC ---

But test is clearly say that podCIDRs must be exist in dualstack?

--- Additional comment from stbenjam on 2021-06-16 14:31:12 UTC ---

Looking at an IPv4 job, I don't see any podIP's either:

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.7-e2e-metal-ipi-virtualmedia/1405130987209232384/artifacts/e2e-metal-ipi-virtualmedia/gather-extra/artifacts/nodes.json


Let's let the OVN team take a look and see what they say about the failures.

--- Additional comment from aconstan on 2021-06-16 14:45:17 UTC ---

We are thinking the session a

--- Additional comment from aojeagar on 2021-06-16 15:24:26 UTC ---

OVN-Kubernetes doesn't support service affinity ... yet, so those tests are a well-known issue and must be skipped

[sig-network] [Feature:IPv6DualStack] [LinuxOnly] Granular Checks: Services Secondary IP Family should function for client IP based session affinity: http
[sig-network] [Feature:IPv6DualStack] [LinuxOnly] Granular Checks: Services Secondary IP Family should function for client IP based 
session affinity: udp


This test can be skipped too, because podCIDRs are not used by OVN, but it is not really an OVN feature.

This happens if the nodeipam controller in the controller-manager is not configured.

[sig-network] [Feature:IPv6DualStack] [LinuxOnly] should have ipv4 and ipv6 node podCIDRs