During 3.9 upgrade process, new quay postgres pod does not created immediately after quay-postgres-upgrade pod completed, it is always waiting for clair-postgres-upgrade pod completed.

If clair-postgres-upgrade pod fails, quay postgres upgrade process will fail as well, even its own upgrade pod is completed.

 quay-operator-bundle-container-v3.9.0-137

Always

1. Setup previous quay version by operator 

   - apiVersion: quay.redhat.com/v1
     kind: QuayRegistry
     metadata:
       name: registry36
       namespace: quay-enterprise-1148
     spec:
       components:
       - kind: clair
         managed: true
       - kind: postgres
         managed: true
       - kind: objectstorage
         managed: false
       - kind: redis
         managed: true
       - kind: horizontalpodautoscaler
         managed: true
       - kind: route
         managed: true
       - kind: mirror
         managed: true
       - kind: monitoring
         managed: true
       - kind: tls
         managed: true
       - kind: quay
         managed: true
       - kind: clairpostgres
         managed: true
       configBundleSecret: test-config-bundle
   

1. Upgrade to quay 3.9
2. Check pod status

new quay postgres pod does not created immediately after quay-postgres-upgrade pod completed, it is always waiting for clair-postgres-upgrade pod completed.

new quay postgres pod should be created immediately after quay-postgres-upgrade pod completed