Bug 2028559

Summary:	OBC stuck on pending post node failure recovery
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	aberner
Component:	Multi-Cloud Object Gateway	Assignee:	Alexander Indenbaum <aindenba>
Status:	CLOSED ERRATA	QA Contact:	aberner
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	belimele, dzaken, ebenahar, etamir, ikave, mmuench, muagarwa, nbecker, nberry, ocs-bugs, odf-bz-bot
Target Milestone:	---	Keywords:	Automation, Regression
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-69	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	2036869 (view as bug list)		Environment:
Last Closed:	2022-04-13 18:50:37 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:
Bug Depends On:
Bug Blocks:	2036869

Description aberner 2021-12-02 15:35:28 UTC

Description of problem (please be detailed as possible and provide log
snippests):
As part of our regression runs, we noticed a failure in several of our runs, related to the creation of OBC post node failure and recovery of the core pod for noobaa.
i.e. - tests/manage/mcg/test_host_node_failure.py::TestNoobaaSTSHostNodeFailure::test_noobaa_sts_host_node_failure[noobaa-core-False]


In order to verify the recovery of the system post node failure (containing the noobaa core pod), we create an obc and write an object on it, however the obc remains on Pending state.


Version of all relevant components (if applicable):
4.9.0-249.ci

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
yes, unable to create a new obc.

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

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

Can this issue reproducible?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1. run test tests/manage/mcg/test_host_node_failure.py::TestNoobaaSTSHostNodeFailure::test_noobaa_sts_host_node_failure[noobaa-core-False]


Actual results:
OBC fails on creation and remains on Pending state.

Expected results:
OBC moves to Bound state and objects can be written on it.

Additional info:
failed runs - 

https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/2402/

https://ocs4-jenkins-csb-ocsqe.apps.ocp4.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/2406/

Comment 15 aberner 2022-01-26 11:01:24 UTC

Verified over:
ocp 4.10.0-0.nightly-2022-01-25-023600
odf 4.10.0-118

Comment 20 errata-xmlrpc 2022-04-13 18:50:37 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 (Important: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & bug fix 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-2022:1372