Bug 1904171

Summary:	RGW Service is unavailable for a short period during upgrade to OCS 4.6
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Travis Nielsen <tnielsen>
Component:	rook	Assignee:	Travis Nielsen <tnielsen>
Status:	CLOSED ERRATA	QA Contact:	Ben Eli <belimele>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.6	CC:	ebenahar, jthottan, madam, muagarwa, ocs-bugs, ratamir
Target Milestone:	---
Target Release:	OCS 4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-17 06:25:30 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 Travis Nielsen 2020-12-03 19:16:32 UTC

Description of problem (please be detailed as possible and provide log
snippests):

During upgrade from OCS 4.5 to 4.6 there is a brief outage for the object store until the upgrade is completed, between the time when the RGW service is updated with some new labels and the RGW pods are updated. For most clusters this may only be a matter of seconds.

Version of all relevant components (if applicable):

OCS 4.5 upgrade to OCS 4.6

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Is there any workaround available to the best of your knowledge?

Wait for the upgrade to complete

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

Can this issue reproducible?

Yes

Can this issue reproduce from the UI?

Yes

If this is a regression, please provide more details to justify this:

Yes, it's a regression in OCS 4.6. A new label was mistakenly added to a matchSelector on the RGW service, which causes the outage.

Steps to Reproduce:
1. Install OCS 4.5
2. Start an object (s3) workload
3. Upgrade to OCS 4.6

Actual results:

The object workload fails briefly while the rgw pods are updating.

Expected results:

Object workloads should continue working while the rgw pod is updating. Without this bug, the workloads can continue since there are two rgw pods and one will serve requests while the other one is updating.

Additional info:

This was found by an upstream user and reported in this issue: https://github.com/rook/rook/issues/6718

Comment 1 Travis Nielsen 2020-12-03 19:17:43 UTC

The fix has already been made upstream and is very low risk, I would like to see it accepted to 4.6.z.

Comment 2 Mudit Agarwal 2020-12-08 16:13:25 UTC

Moving it back to 4.6.0 as decided in pgm meeting.

Travis, please merge the backport PR to 4.6

Comment 7 Elad 2020-12-16 13:35:41 UTC

Moving to VERIFIED based on OCS 4.6 RC7 regression cycle automation runs

Comment 9 errata-xmlrpc 2020-12-17 06:25:30 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 (Moderate: Red Hat OpenShift Container Storage 4.6.0 security, bug fix, enhancement 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/RHSA-2020:5605