Bug 2187914

Summary: [GSS][OCS 4.9] Nooba pod noobaa-db-pg-0 CLBO exit code 1
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Rafrojas <rafrojas>
Component: Multi-Cloud Object GatewayAssignee: Nimrod Becker <nbecker>
Status: CLOSED NOTABUG QA Contact: krishnaram Karthick <kramdoss>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: hnallurv, mduasope, nbecker, ocs-bugs, odf-bz-bot
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-05-22 07:40:09 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 Rafrojas 2023-04-19 06:21:03 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
Pod noobaa-db-pg-0 in openshift-storage project restarts continuously with exit code 1


Version of all relevant components (if applicable):
NAME                           DISPLAY                            VERSION   REPLACES                   PHASE
datagrid-operator.v8.3.7       Data Grid                          8.3.7     datagrid-operator.v8.3.6   Succeeded
dynatrace-operator.v0.9.1      Dynatrace Operator                 0.9.1                                Succeeded
elasticsearch-operator.5.5.0   OpenShift Elasticsearch Operator   5.5.0                                Succeeded
mcg-operator.v4.9.10           NooBaa Operator                    4.9.10    mcg-operator.v4.9.9        Succeeded
ocs-operator.v4.9.10           OpenShift Container Storage        4.9.10    ocs-operator.v4.9.9        Succeeded
odf-operator.v4.9.10           OpenShift Data Foundation          4.9.10    odf-operator.v4.9.9        Succeeded

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


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


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


Can this issue reproducible?
Is continuously restarting

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: