Bug 1833145 - During an upgrade of the ES cluster traffic is still allowed to flow in
Summary: During an upgrade of the ES cluster traffic is still allowed to flow in
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.5.0
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-07 21:47 UTC by ewolinet
Modified: 2020-07-13 17:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:35:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 347 0 None closed Bug 1833145: Set network policy when doing upgrades to prevent connections 2020-06-24 02:06:07 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:36:19 UTC

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