Bug 2148370

Summary:	noobaa-db-pg-0 pod is in init state after rescheduling to a new healthy worker node on IBM Power
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Sudeesh John <sjohn>
Component:	csi-driver	Assignee:	Madhu Rajanna <mrajanna>
Status:	CLOSED NOTABUG	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.12	CC:	dzaken, ebenahar, etamir, madam, mrajanna, muagarwa, ocs-bugs, odf-bz-bot
Target Milestone:	---
Target Release:	---
Hardware:	ppc64le
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-13 07:41:32 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 Sudeesh John 2022-11-25 09:00:06 UTC

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

noobaa-db-pg-0 pod is in init state after rescheduling to a new healthy worker node on IBM Power

Version of all relevant components (if applicable):

ODF 4.12 and OCP 4.12


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

No.

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

Bring back the NotReady node to Ready state

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

1

Can this issue reproducible?
Yes


Can this issue reproduce from the UI?

No.

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

Yes.


Steps to Reproduce:
1. Bring down the worker node where noobaa-db-pg-0 running 
2. and Observe noobaa-db-pg-0 pod



Actual results:

noobaa-db-pg-0 Pod is in init state on the rescheduled worker node.


Expected results:

noobaa-db-pg-0 Pod should start running in the rescheduled Worker

Additional info:


Mustgather: https://drive.google.com/file/d/1U2fPzGG7ogP5IC9r4Dz4jrSsiEawNAh0/view?usp=share_link

Comment 2 Sudeesh John 2022-12-01 06:19:39 UTC

As the Object Store functionality would be broken if the node on which noobaa-db-pg-0 pod is running is down, I request to move this to a blocker for 4.12

Comment 3 Elad 2022-12-01 07:35:19 UTC

Proposing as a blocker for 4.12.0 as per comment #2