Bug 1908290 - [4.6.6] Route is accessible before pod became ready
Summary: [4.6.6] Route is accessible before pod became ready
Keywords:
Status: CLOSED DUPLICATE of bug 1904010
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6.z
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: aos-network-edge-staff
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-16 10:39 UTC by Kyrylo
Modified: 2022-08-04 22:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 17:41:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.