-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.6.0
Description:
This is an issue found when upgrade Quay from Quay 3.3.4 to Quay 3.6.0, after migration was triggered, the postgres migration POD was failed to start with error message "error: a container name must be specified for pod quay33-quay-postgres-migration-5474f55d8f-tjsc4, choose one of: [quay-postgres-migration quay-postgres-migration-cleanup] or one of the init containers: [quay-postgres-migration-init]", refer to Quay Operator POD logs quay_360_operator_pod.logs
Note:
- Quay 3.6.0 image is "quay-operator-bundle-container-v3.6.0-41", see https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1742608
- This is a regression issue which is not existed previous Quay 3.6.0 image "quay-operator-bundle-container-v3.6.0-02"
oc get pod NAME READY STATUS RESTARTS AGE quay-operator.v3.6.0-6f486ff876-mklbz 1/1 Running 0 15m quay33-clair-7b98985b96-vs8c2 1/1 Running 0 65m quay33-clair-postgresql-6b95d77879-4zx7b 1/1 Running 0 65m quay33-quay-5989d848f5-f5jwg 1/1 Running 0 66m quay33-quay-config-64c5957879-dzb45 1/1 Running 0 66m quay33-quay-postgres-migration-5474f55d8f-tjsc4 0/2 Init:CrashLoopBackOff 4 2m44s quay33-quay-postgresql-549d5d6f5-rrmbr 1/1 Running 0 67m quay33-quay-postgresql-9ff4646c5-dp8fh 0/1 ContainerCreating 0 13m quay33-quay-repomirror-6bcbc95bcb-48x2r 1/1 Running 0 65m quay33-redis-5bd7c8d864-92758 1/1 Running 0 68m oc logs quay33-quay-postgres-migration-5474f55d8f-tjsc4 error: a container name must be specified for pod quay33-quay-postgres-migration-5474f55d8f-tjsc4, choose one of: [quay-postgres-migration quay-postgres-migration-cleanup] or one of the init containers: [quay-postgres-migration-init] oc get pod quay-operator.v3.6.0-6f486ff876-mklbz -o json | jq '.spec.containers[0].image' "registry.redhat.io/quay/quay-operator-rhel8@sha256:0246f732ab81801f8f6b17369641f95400239d49472a34f4009cb6bccfecbf6f"
Quay 3.3.4 CR:
kind: QuayEcosystem metadata: name: quay33 spec: quay: imagePullSecretName: redhat-pull-secret enableRepoMirroring: true image: quay.io/quay/quay:v3.3.4-2 registryBackends: - name: default s3: accessKey: ****** bucketName: quay330 secretKey: ****** host: s3.us-east-2.amazonaws.com externalAccess: hostname: quayv33.apps.quay-perf-796.perfscale.devcluster.openshift.com tls: secretName: quay33tls termination: passthrough database: volumeSize: 30Gi envVars: - name: DEBUGLOG value: "true" clair: enabled: true image: quay.io/quay/clair-jwt:v3.3.4-1 imagePullSecretName: redhat-pull-secret
Steps:
- Deploy Quay 3.3.4 with Quay 3.3.4 Operator
- Upgrade Quay 3.3.4 Operator to Quay 3.6.0
- Update Quay 3.3 QuayEcosystem CR with "quay-operator/migrate: "true"
- Check Quay migration status
Expected Results:
QuayEcosytem should be migrated to QuayRegistry successfully.
Actual Results:
QuayEcosytem was failed to migrated to QuayRegistry
