Bug 1833145

Summary:	During an upgrade of the ES cluster traffic is still allowed to flow in
Product:	OpenShift Container Platform	Reporter:	ewolinet
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.5	CC:	aos-bugs, qitang, wking
Target Milestone:	---
Target Release:	4.5.0
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:	2020-07-13 17:35:59 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 ewolinet 2020-05-07 21:47:33 UTC

Description of problem:
While the EO is upgrading the ES cluster, traffic from log collectors is still allowed to flow in, complicating the upgrade due to waiting for the cluster to be Green before continuing to the next nodee.

Version-Release number of selected component (if applicable):
4.5

How reproducible:
Always

Comment 3 Anping Li 2020-06-01 14:42:50 UTC

Move to Verified as we blocked all traffic by network policy.

Comment 4 W. Trevor King 2020-06-01 18:16:44 UTC

I'm removing UpgradeBlocker, because it's not clear to me why we'd block OCP updates based on this bug.  If folks think that this does deserve removing 4.3 -> 4.4 or other recommended update recommendations from Cincinnati, please explain why and restore the keyword.

Comment 5 errata-xmlrpc 2020-07-13 17:35:59 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-2020:2409