Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-2319

Quay Operator managed postgresql database POD failed to start

XMLWordPrintable

      Description:

      This is an issue found when deploy Quay with Quay 3.6.0 Operator, by using managed postgres component, after created QuayRegistry, found quay postgresql database POD was failed to start, get error "ERROR: tuple already updated by self", pls check this issue.

      Note: Quay image is quay-registry-container-v3.6.0-20

      https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1678139 

      Quay PODs:

      oc get pod
      NAME                                          READY   STATUS             RESTARTS   AGE
      quay-operator.v3.6.0-64b74f4f7f-flfrk         1/1     Running            0          7m27s
      quay360-clair-app-5946967db7-c2jwc            1/1     Running            0          3m26s
      quay360-clair-app-5946967db7-pmmf2            1/1     Running            0          3m29s
      quay360-clair-postgres-764cfdb568-jc7xs       1/1     Running            0          2m47s
      quay360-quay-app-ff96fdfb8-22zh8              0/1     Running            0          3m27s
      quay360-quay-app-ff96fdfb8-qgt78              0/1     Running            0          3m29s
      quay360-quay-app-upgrade-w4lqt                0/1     Completed          0          4m9s
      quay360-quay-config-editor-866ccfd7d6-x42lk   1/1     Running            0          3m29s
      quay360-quay-database-65c76f6868-xqsw4        0/1     CrashLoopBackOff   4          3m29s
      quay360-quay-mirror-756d8fcb4c-29gck          0/1     Init:0/1           1          2m47s
      quay360-quay-mirror-756d8fcb4c-66q6m          0/1     Init:0/1           1          2m47s
      quay360-quay-postgres-init-9fk82              0/1     Completed          0          3m33s
      quay360-quay-redis-6cf5f4d4d6-b7qfv           1/1     Running            0  
      
      oc get pod quay360-quay-database-65c76f6868-xqsw4 -o json | jq '.spec.containers[0].image'
      "registry.redhat.io/rhel8/postgresql-10@sha256:8c477078782dc1f66142014ab147da47ab2c3f08e12ecab2efa5e97fa028d4d1"
              
      oc logs quay360-quay-database-65c76f6868-xqsw4
      pg_ctl: another server might be running; trying to start server anyway
      waiting for server to start....2021-08-02 02:23:45.550 UTC [22] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
      2021-08-02 02:23:45.560 UTC [22] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
      2021-08-02 02:23:45.636 UTC [22] LOG:  redirecting log output to logging collector process
      2021-08-02 02:23:45.636 UTC [22] HINT:  Future log output will appear in directory "log".
       done
      server started
      /var/run/postgresql:5432 - accepting connections
      => sourcing /usr/share/container-scripts/postgresql/start/set_passwords.sh ...
      ERROR:  tuple already updated by self
      

              rmarasch@redhat.com Ricardo Maraschini (Inactive)
              lzha1981 luffy zhang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: