Bug 2187914 - [GSS][OCS 4.9] Nooba pod noobaa-db-pg-0 CLBO exit code 1
Summary: [GSS][OCS 4.9] Nooba pod noobaa-db-pg-0 CLBO exit code 1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-19 06:21 UTC by Rafrojas
Modified: 2023-08-09 16:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-22 07:40:09 UTC
Embargoed:


Attachments (Terms of Use)

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:


Note You need to log in before you can comment on or make changes to this bug.