Bug 2262461

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

This is a Standalone MCG deployment, after creating the storagecluster the noobaa-db-pg-0 transitions to CrashLoopBackOff status. Nothing is logged in noobaa-db-pg-0 container, the only logging we see is from the init container initialize-database

current.log
2024-02-02T21:26:16.898502462Z + export PGDATA=/var/lib/pgsql/data/userdata
2024-02-02T21:26:16.898502462Z + PGDATA=/var/lib/pgsql/data/userdata
2024-02-02T21:26:16.898502462Z + '[' -f /var/lib/pgsql/data/userdata/postgresql.conf ']'
2024-02-02T21:26:16.898502462Z + p=/opt/rh/rh-postgresql12/root/usr/bin/postgres
2024-02-02T21:26:16.898502462Z + '[' '!' -x /opt/rh/rh-postgresql12/root/usr/bin/postgres ']'
2024-02-02T21:26:16.898502462Z + p=/usr/bin/postgres
2024-02-02T21:26:16.898502462Z + mv /usr/bin/postgres /usr/bin/postgres.orig
2024-02-02T21:26:16.901596949Z + echo exec /usr/bin/postgres.orig '"$@"' -c huge_pages=off
2024-02-02T21:26:16.901750510Z + chmod 755 /usr/bin/postgres
2024-02-02T21:26:16.903686201Z + sed -i -e 's/^\(postgres:[^:]\):[0-9]*:[0-9]*:/\1:10001:0:/' /etc/passwd
2024-02-02T21:26:16.905541628Z + sed -i -e 's/^exec.*$/exit 0/' -e 's/^pg_ctl\sstart.*/pg_ctl start || true/' /usr/bin/run-postgresql
2024-02-02T21:26:16.907360673Z + su postgres -c 'bash -x /usr/bin/run-postgresql'
2024-02-02T21:26:16.917681183Z + export ENABLE_REPLICATION=false
2024-02-02T21:26:16.917681183Z + ENABLE_REPLICATION=false
2024-02-02T21:26:16.917681183Z + set -eu
2024-02-02T21:26:16.918069281Z ++ cgroup-limits
~
 

Version of all relevant components (if applicable):
4.12.10

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

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

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?
Yes, on the customer site

Can this issue reproduce from the UI?
N/A


Additional info:

We were able to modify noobaa-db-pg-0 sts adding following command to init container and access contianer using oc rsh init noobaa-db-pg-0
 
- command: - /bin/sh - -ec - while :; do echo '.'; sleep 3600 ; done