Bug 2209071

Summary:	[GSS][ODF 4.10] unable to start pod noobaa-db-pg-0
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	amansan <amanzane>
Component:	ceph	Assignee:	Ilya Dryomov <idryomov>
ceph sub component:	RBD	QA Contact:	Elad <ebenahar>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	high
Priority:	high	CC:	bniver, dzaken, hnallurv, muagarwa, nbecker, ocs-bugs, odf-bz-bot, sostapov, vumrao
Version:	4.10	Flags:	dzaken: needinfo-
Target Milestone:	---
Target Release:	---
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:	2023-06-19 10:57:25 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 amansan 2023-05-22 13:43:58 UTC

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

The datastore got full at VMware, the customer reclaimed the space and after that the noobaa-db-pg-0 is unable to start dueinconsistency in the device


Version of all relevant components (if applicable):

ODF 4.10


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

The customer can’t start the pods using noobaa


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?

No

Can this issue reproduce from the UI?


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


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info: