Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1855895

Summary:	Egress Router pod is stuck in Init:CrashLoopBackOff
Product:	OpenShift Container Platform	Reporter:	Ben Bennett <bbennett>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	openshift-sdn	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	aconstan, anbhat, anusaxen, bbennett, ckoep, danw, dcbw, mifiedle, nraghava, pstrick, rkhan, weliang, zzhao
Version:	4.1.z	Keywords:	ServiceDeliveryImpact
Target Milestone:	---
Target Release:	4.4.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SDN-CI-IMPACT,SDN-STALE
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1855894	Environment:
Last Closed:	2020-08-18 11:45:28 UTC	Type:	---
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:	1855894
Bug Blocks:

Comment 4 Weibin Liang 2020-08-10 18:47:22 UTC

Tested and verified in 4.4.0-0.nightly-2020-08-10-015804

oc logs -c egress-router egress-redirect-pod will not see below error any more:
iptables v1.4.21: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)

Comment 6 errata-xmlrpc 2020-08-18 11:45:28 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 (OpenShift Container Platform 4.4.17 bug fix update), 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-2020:3334