[BUG] Postgresql cluster is always Creating status when new create

[taylor840326]

Describe the bug
Postgresql cluster is always Creating status.

To Reproduce
Steps to reproduce the behavior:

1. Create postgresql cluster.

 kbcli cluster create --cluster-definition postgresql --cluster-version postgresql-16.4.0  ipsql16

2. Connect to postgresql cluster is ok.

kbcli cluster connect ipsql16

4. Postgresql slave instance is not ready on k8s.

kubectl get pods   
ipsql16-postgresql-1          3/4     Running   0             6h38m

6. kubectl logs get some errors

 No such file or directory: '/home/postgres/pgdata/pgroot/data/postmaster.opts'"

Expected behavior
Postgresql cluster status is Running.

Screenshots

Desktop (please complete the following information):

• Kubernetes: v1.29.5+k3s1
• KubeBlocks: 0.9.0
• kbcli: 0.9.0

[shanshanying]

hi @taylor840326 ,

thanks for reporting the bug. We fill fix is ASAP.

[ldming]

Hi @taylor840326, I tried to reproduce this issue but was unable to do so. I suspect that there might have been a problem during initdb initializing the data directory, which led to the startup failure. Could you please provide the complete logs for this pod?

[taylor840326]

Hi @taylor840326, I tried to reproduce this issue but was unable to do so. I suspect that there might have been a problem during initdb initializing the data directory, which led to the startup failure. Could you please provide the complete logs for this pod?

[ldming]

Hi @taylor840326, I tried to reproduce this issue but was unable to do so. I suspect that there might have been a problem during initdb initializing the data directory, which led to the startup failure. Could you please provide the complete logs for this pod?

Are there more logs?

[taylor840326]

Hi @taylor840326, I tried to reproduce this issue but was unable to do so. I suspect that there might have been a problem during initdb initializing the data directory, which led to the startup failure. Could you please provide the complete logs for this pod?

Are there more logs?

Hi @ldming ，I have solved this problem. The reason is that “Huge Page“ causes the database command execute failure

initdb 

... Bus error ...

I create a cluster using the following command.

Add "limits.hugepages-2Mi=1024Mi" parameter

cat <<EOF | kubectl apply -f -
apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
  name: psql16
  namespace: demo
spec:
  clusterDefinitionRef: postgresql
  clusterVersionRef: postgresql-16.4.0
  terminationPolicy: Delete
  affinity:
    podAntiAffinity: Preferred
    topologyKeys:
    - kubernetes.io/hostname
  tolerations:
    - key: kb-data
      operator: Equal
      value: 'true'
      effect: NoSchedule
  componentSpecs:
  - name: postgresql
    componentDefRef: postgresql
    enabledLogs:
    - running
    disableExporter: true
    replicas: 2
    resources:
      limits:
        cpu: '0.5'
        memory: 0.5Gi
        hugepages-2Mi: 1024Mi
      requests:
        cpu: '0.5'
        memory: 0.5Gi
    volumeClaimTemplates:
    - name: data
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 20Gi
EOF

refer to: https://www.percona.com/blog/using-huge-pages-with-postgresql-running-inside-kubernetes/