-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.6.0
Description:
This is an issue found when upgrade from Quay 3.3.4 to Quay 3.6.0, when in Quay 3.3.4 the tls termination is none, that means customer is using http, then after upgrade, the quay route is still point to quay 3.3 service, and there's no config editor route, builder route created for 3.6.0 QuayRegistry, refer to Quay 3.6.0 Operator POD logs quay_3.6.0_operator_upgraede_from_334_pod.logs
Note: Quay 3.6.0 image is "quay-operator-bundle-container-v3.6.0-43"
Quay 3.3.4 QuayEcosystem CR:
apiVersion: redhatcop.redhat.io/v1alpha1 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: termination: none 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
After upgrade to Quay 3.6.0:
oc get pod
NAME READY STATUS RESTARTS AGE
quay-operator.v3.6.0-5dcbfccbc6-qbds2 1/1 Running 0 32m
quay33-clair-77c8fcf45d-9xp2l 1/1 Running 0 41m
quay33-clair-app-b88b6f6d6-5dzmv 1/1 Running 0 3m12s
quay33-clair-app-b88b6f6d6-8lsms 1/1 Running 0 3m16s
quay33-clair-postgres-5468fb79d8-wz7hs 1/1 Running 1 3m38s
quay33-clair-postgresql-6b95d77879-mrq2f 1/1 Running 0 42m
quay33-quay-5b69c4d97-nnfpw 1/1 Running 1 43m
quay33-quay-app-86564fd87f-4wp64 1/1 Running 1 3m8s
quay33-quay-app-86564fd87f-n5bkg 1/1 Running 2 3m17s
quay33-quay-app-upgrade-b8b9p 0/1 Completed 0 3m24s
quay33-quay-config-64c5957879-52ml5 1/1 Running 0 43m
quay33-quay-config-editor-58d74d7dc-n7dpz 1/1 Running 0 3m16s
quay33-quay-database-8d994dfb4-qf8tn 1/1 Running 0 3m38s
quay33-quay-mirror-785b4b454f-4dcw5 1/1 Running 0 2m38s
quay33-quay-mirror-785b4b454f-9n4pr 1/1 Running 0 2m38s
quay33-quay-postgres-init-9r24q 0/1 Completed 0 3m17s
quay33-quay-postgresql-9ff4646c5-4frh2 1/1 Running 0 5m12s
quay33-quay-redis-5ff67c5dcb-jvhf6 1/1 Running 0 3m38s
quay33-quay-repomirror-6bcbc95bcb-q5d5m 1/1 Running 0 42m
quay33-redis-5bd7c8d864-m5ks2 1/1 Running 0 45m
oc get route
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
quay33-quay quayv33.apps.quay-perf-796.perfscale.devcluster.openshift.com quay33-quay 8080 None
quay33-quay-config quay33-quay-config-quay334.apps.quay-perf-796.perfscale.devcluster.openshift.com quay33-quay-config 8443 passthrough/Redirect None
Steps:
- Deploy Quay 3.3.4 with TLS termination as none
- Upgrade Quay Operator to 3.6.0
- Change subscription channel to stable-3.6.0
- trigger Quay Upgrade
Expected Results:
Quay upgrade completed successfully, quay route point to Quay 3.6.0 app service, config editor route, builder route are created correctly.
Actual Results:
Quay upgrade completed successfully, but quay route still point to Quay 3.3.4 app service, config editor route, builder route are not created.
