Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2244405

Summary: [OVN][Shift on Stack] One of Shift master nodes doesn't receive TCP SYN segments on ports 9641 and 9642
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Alex Stupnikov <astupnik>
Component: ovn22.12Assignee: Dumitru Ceara <dceara>
Status: CLOSED DUPLICATE QA Contact: Jianlin Shi <jishi>
Severity: urgent Docs Contact:
Priority: medium    
Version: FDP 23.ICC: apevec, ctrautma, dceara, ihrachys, i.maximets, jfindysz, jiji, lhh, lmartins, majopela, mmichels, sboyron, scohen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-30 18:44:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alex Stupnikov 2023-10-16 11:33:42 UTC 
Description of problem:

One of our customers runs OpenShift on top of RHOSP 16.2 and faced strange problem: one of master nodes is unable to receive TCP SYN segments on ports 9641 and 9642 because they are dropped somewhere on br-int on compute hosts. Other communication flows are not affected and remaining master nodes were not affected by this problem.

Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform release 16.2.1 

How reproducible:
Unclear, communication on these ports is established sporadically. Failure was reported after timezone and NTP settings were changed on Shift master and this change likely triggered communication reset. Actual problem may occur much sooner.

Additional info:
Will be provided privately.
Comment 18 Dumitru Ceara 2023-10-30 18:44:18 UTC 

*** This bug has been marked as a duplicate of bug 2071272 ***