-
Bug
-
Resolution: Unresolved
-
Major
-
4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z, 4.18.z, 4.19.0
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
None
-
Rejected
-
CORENET Sprint 273, CORENET Sprint 274, CORENET Sprint 275
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
CVE-2024-11614 is starting to show up in grading reports, e.g. in this 4.14: https://errata.devel.redhat.com/errata/container/148479
This CVE is fixed in 3.3 with openvswitch3.3-3.3.0-92.el9fdp. Unsure if there is a fix for 3.4 and 3.5 and 2.17. For reference, these are the current ovs pins:
ovn-kubernetes-base_4.12_Dockerfile 2.17.0-148.el8fdp ovn-kubernetes-base_4.14_Dockerfile 3.3.0-62.el9fdp ovn-kubernetes-base_4.15_Dockerfile 3.3.0-62.el9fdp ovn-kubernetes-base_4.16_Dockerfile 3.3.0-62.el9fdp ovn-kubernetes-base_4.17_Dockerfile 3.4.0-18.el9fdp ovn-kubernetes-base_4.18_Dockerfile 3.4.0-18.el9fdp ovn-kubernetes-base_4.19_Dockerfile 3.5.0-0.9.el9fdp ovn-kubernetes-base_4.20_Dockerfile 3.5
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