-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.0
-
Important
-
None
-
Proposed
-
False
-
Description of problem:
when setting the joinSubnets in UserDefinedNetwork
apiVersion: k8s.ovn.org/v1
kind: UserDefinedNetwork
metadata:
name: l3-primary
spec:
topology: Layer3
layer3:
role: Primary
joinSubnets:
- 100.100.100.0/16
- fd91::/64
mtu: 1300
subnets:
- cidr: "20.100.0.0/16"
hostSubnet: 24
- cidr: "2010:100:0::0/48"
hostSubnet: 64
- oc get net-attach-def -n z5 -o yaml
apiVersion: v1
items:
- apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
creationTimestamp: "2024-11-13T03:25:49Z"
finalizers:
- k8s.ovn.org/user-defined-network-protection
generation: 1
labels:
k8s.ovn.org/user-defined-network: ""
name: l3-primary
namespace: z5
ownerReferences:
- apiVersion: k8s.ovn.org/v1
blockOwnerDeletion: true
controller: true
kind: UserDefinedNetwork
name: l3-primary
uid: 3ea70556-e1a3-40d4-8067-0849f06ffcb8
resourceVersion: "359320"
uid: 51f79383-c0e2-47d0-a63a-4a1754bf9d57
spec:
config: '{"cniVersion":"1.0.0","joinSubnets":"100.100.100.0/16,fd91::/64","mtu":1300,"name":"z5.l3-primary","netAttachDefName":"z5/l3-primary","role":"primary","subnets":"20.100.0.0/16/24,2010:100:0::0/48/64","topology":"layer3","type":"ovn-k8s-cni-overlay"}'
kind: List
metadata:
resourceVersion: ""
The static route still using the default value
sh-5.1# ovn-nbctl lr-route-list z5.l3.primary_ovn_cluster_router
IPv4 Routes
Route Table <main>:
100.65.0.2 100.88.0.2 dst-ip
100.65.0.3 100.88.0.3 dst-ip
100.65.0.4 100.88.0.4 dst-ip
100.65.0.5 100.88.0.5 dst-ip
100.65.0.6 100.88.0.6 dst-ip
100.65.0.7 100.65.0.7 dst-ip
172.30.0.10 20.100.0.2 dst-ip
20.100.1.0/24 100.88.0.2 dst-ip
20.100.2.0/24 100.88.0.3 dst-ip
20.100.3.0/24 100.88.0.4 dst-ip
20.100.4.0/24 100.88.0.5 dst-ip
20.100.5.0/24 100.88.0.6 dst-ip
20.100.0.0/24 100.65.0.7 src-ip
IPv6 Routes
Route Table <main>:
fd99::2 fd97::2 dst-ip
fd99::3 fd97::3 dst-ip
fd99::4 fd97::4 dst-ip
fd99::5 fd97::5 dst-ip
fd99::6 fd97::6 dst-ip
fd99::7 fd99::7 dst-ip
2010:100:0:2::/64 fd97::2 dst-ip
2010:100:0:3::/64 fd97::3 dst-ip
2010:100:0:4::/64 fd97::4 dst-ip
2010:100:0:5::/64 fd97::5 dst-ip
2010:100:0:6::/64 fd97::6 dst-ip
2010:100:0:1::/64 fd99::7 src-ip
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.
Affected Platforms:
Is it an
- internal CI failure
- customer issue / SD
- internal RedHat testing failure
If it is an internal RedHat testing failure:
- Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).
If it is a CI failure:
- Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
- Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
- Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
- When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
- If it's a connectivity issue,
- What is the srcNode, srcIP and srcNamespace and srcPodName?
- What is the dstNode, dstIP and dstNamespace and dstPodName?
- What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
If it is a customer / SD issue:
- Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
- Don’t presume that Engineering has access to Salesforce.
- Do presume that Engineering will access attachments through supportshell.
- Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
- Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
- If the issue is in a customer namespace then provide a namespace inspect.
- If it is a connectivity issue:
- What is the srcNode, srcNamespace, srcPodName and srcPodIP?
- What is the dstNode, dstNamespace, dstPodName and dstPodIP?
- What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
- Please provide the UTC timestamp networking outage window from must-gather
- Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
- If it is not a connectivity issue:
- Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.
- When showing the results from commands, include the entire command in the output.
- For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
- For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
- Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
- Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
- For guidance on using this template please see
OCPBUGS Template Training for Networking components
