| |
Original: Description of problem: With spec.gatewayConfig.routingViaHost=true, configured static route on worker node to route data and control flow.
The static routes work fine when we make tests from nodes to an external smtp server (ping, netcat, ...), but when we do the test from a pod on the same node we cannot connect to the external smtp server.
There is an issue with static routes that are not applied on the pods.
Attempted solution in support article: https://access.redhat.com/solutions/6962558
Version-Release number of selected component (if applicable): 4.14
How reproducible: Easy
Steps to Reproduce:
1. Modify routingViaHost=true in spec.gatewayConfig.routingViaHost=true via
$ oc patch network.operator/cluster --type merge -p '{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"gatewayConfig":
{"routingViaHost":true}
}}}}'
2. Confirm changes and send application traffic
3.
Actual results: Cannot reach traffic through the bond 1.1451, all network traffic routed through br-ex works without issue
Expected results: Traffic off of the bond 1.1451 interface is sent successfully.
Additional info: Ref: Salesforce Case No. 03805126
Affected namespace inspect: https://attachments.access.redhat.com/hydra/rest/cases/03805126/attachments/80c1c8df-a02a-4e85-84a3-b440de523eb1?usePresignedUrl=true
Sos-report of a host with the issue:
https://attachments.access.redhat.com/hydra/rest/cases/03805126/attachments/02f43fe8-953b-4b9f-b7d0-8add05b666e2?usePresignedUrl=true
Must-gather of cluster:
https://attachments.access.redhat.com/hydra/rest/cases/03805126/attachments/31d6c175-6fb5-4673-b436-95eaf86fc11b?usePresignedUrl=true
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
# customer issue / SD
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.
* Please provide must-gather and sos-report with an exact link to the comment in the support case with the attachment. The format should be: [https://access.redhat.com/support/cases/#/case/]<case number>/discussion?attachmentId=<attachment id>
* Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
* When showing the results from commands, include the entire command in the output.
* 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.
* 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, labels with “sbr-untriaged”
* Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template” |
Bug
Normal
