Bug 1927885

Summary:	OCS 4.7: ocs operator pod in 1/1 state even when Storagecluster is in Progressing state
Product:	[Red Hat Storage] Red Hat OpenShift Container Storage	Reporter:	Neha Berry <nberry>
Component:	ocs-operator	Assignee:	Renan Campos <rcampos>
Status:	CLOSED ERRATA	QA Contact:	Neha Berry <nberry>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.7	CC:	ebenahar, jarrpa, madam, muagarwa, ocs-bugs, sostapov
Target Milestone:	---	Keywords:	AutomationBackLog, Regression
Target Release:	OCS 4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.7.0-262.ci	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-19 09:20:00 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:

Comment 3 Jose A. Rivera 2021-02-11 18:04:22 UTC

We have a pretty good idea of what happened. This is absolutely a regression and will have to be fixed. Verification should be fairly straightforward.

Comment 4 Jose A. Rivera 2021-02-11 18:13:29 UTC

Setting priority to urgent since this is a blocker for OSD testing.

Comment 10 Renan Campos 2021-02-22 15:22:17 UTC

I have manually tested the behaviour of 4.7 and compared it with 4.6. For the case that this bug was made for and edge cases such as bringing down axillary operator pods, the ocs-operator in 4.7 behaves the same way as it did in 4.6.

Comment 14 errata-xmlrpc 2021-05-19 09:20:00 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.7.0 security, bug fix, and 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-2021:2041