Bug 1699341

Summary: Synchronization firewall rules takes up to 90min
Product: OpenShift Container Platform Reporter: sperezto
Component: NetworkingAssignee: Casey Callendrello <cdc>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: urgent CC: aos-bugs, cdc, danw, dcbw, huirwang, jack.ottofaro, openshift-bugs-escalate, piqin, rbinkhor, scuppett, simon.gerber, tobias.brunner, weliang
Version: 3.9.0   
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1734003 1734009 (view as bug list) Environment:
Last Closed: 2019-10-16 06:28:05 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:
Bug Depends On:    
Bug Blocks: 1734003, 1734009    

Comment 30 Weibin Liang 2019-07-31 12:54:12 UTC 
The PR https://github.com/openshift/origin/pull/23426 is still in open state.

Change status back to assigned
Comment 31 Dan Winship 2019-08-01 15:41:15 UTC 
origin#23426 is the PR for 3.11. The 4.2 PR is sdn#8, and it's merged
Comment 33 Weibin Liang 2019-08-02 18:01:46 UTC 
Verifying this bug is blocked by below bug:

Bug 1737127 - oc idle service cause runtime error: invalid memory address or nil pointer dereference
Comment 34 Casey Callendrello 2019-08-05 12:27:45 UTC 
Weibin,
We'll fix that. In the mean time, you can make progress on this by using an older "oc" binary (e.g. from 4.1). That bug is unrelated to this code.
Comment 35 zhaozhanqi 2019-08-05 12:44:02 UTC 
thanks your suggestion from comment 28

Following your steps. all service work well. So verified this bug.
Comment 36 errata-xmlrpc 2019-10-16 06:28:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922