Bug 1908290

Summary:	[4.6.6] Route is accessible before pod became ready
Product:	OpenShift Container Platform	Reporter:	Kyrylo <kshpak>
Component:	Networking	Assignee:	aos-network-edge-staff <aos-network-edge-staff>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	amcdermo, aos-bugs
Version:	4.6.z
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-17 17:41:44 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 Kyrylo 2020-12-16 10:39:36 UTC

Description of problem:
Router exposes the pod publicly, even though the pod isn't marked as ready.
Therefore route is responding HTTP/200OK while the pod's "Ready" state is still 0/1


Version-Release number of selected component (if applicable):
OCP 4.6.6 (stable 4.6)


Additional info:
OCP cluster deployed on OpenStack

Comment 1 Andrew McDermott 2020-12-17 17:41:44 UTC

This looks identical to https://bugzilla.redhat.com/show_bug.cgi?id=1904010 and the fix for that landed in 4.6.8. See the errata: https://access.redhat.com/errata/RHSA-2020:5259.

I'm going to mark this as a duplicate but please reopen if this is not the case.

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