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
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
Proposing as a blocker for 4.12.0 as per comment #2