-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.19.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
No
-
2025-03-31: Blocker for BGP GA in 4.19.0
-
None
-
Rejected
-
None
-
In Progress
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Description of problem:
setup cluster and enable BGP and config vrf-lite as below show
[root@openshift-qe-045 ~]# curl --interface blue.100 40.100.3.6:8080 Hello OpenShift! [root@openshift-qe-045 ~]# ip route show table 100 40.100.1.0/24 nhid 3181 via 192.168.100.1 dev blue.100 proto bgp metric 20 40.100.3.0/24 nhid 3183 via 192.168.100.2 dev blue.100 proto bgp metric 20 192.168.100.0/24 dev blue.100 proto kernel scope link src 192.168.100.3 local 192.168.100.3 dev blue.100 proto kernel scope host src 192.168.100.3 broadcast 192.168.100.255 dev blue.100 proto kernel scope link src 192.168.100.3 ####pod [root@openshift-qe-045 ~]# oc get pod -n z5 -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES test-rc-kr45b 1/1 Running 0 20m 10.129.2.190 worker-2 <none> <none> test-rc-wrhsp 1/1 Running 0 20m 10.131.0.94 worker-0 <none> <none> [root@openshift-qe-045 ~]# oc rsh -n z5 test-rc-kr45b ~ $ ~ $ ~ $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0@if316: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP group default link/ether 0a:58:0a:81:02:be brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.129.2.190/23 brd 10.129.3.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::858:aff:fe81:2be/64 scope link valid_lft forever preferred_lft forever 3: ovn-udn1@if317: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc noqueue state UP group default link/ether 0a:58:28:64:03:06 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 40.100.3.6/24 brd 40.100.3.255 scope global ovn-udn1 valid_lft forever preferred_lft forever inet6 fe80::858:28ff:fe64:306/64 scope link valid_lft forever preferred_lft forever ~ $ curl www.google.com -I --connect-timeout 3 curl: (28) Failed to connect to www.google.com port 80 after 2960 ms: Operation timed out
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
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update