-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
quay-v3.11.0
-
False
-
Not a blocker, we should investigate the reason though
-
False
-
-
-
0
-
Proposed
Description of problem:
Upgrade from 3.8 to 3.11, only quay operator upgrade, quay registry do not upgrade, keep still there.
note: 3.9/3.10 -> 3.11 works, not find this issue
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.11.0-28
How reproducible:
Always
Steps to Reproduce:
- Setup latest quay 3.8 version by operator
- apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quayregistry namespace: quay-enterprise-14660 spec: components: - kind: clair managed: true - kind: postgres managed: true - kind: objectstorage managed: true - kind: redis managed: true - kind: horizontalpodautoscaler managed: true - kind: route managed: true - kind: mirror managed: true - kind: monitoring managed: false - kind: tls managed: true - kind: quay managed: true - kind: clairpostgres managed: true configBundleSecret: test-config-bundle
- Upgrade to quay 3.11
- Check pod status
Actual Results:
- Quay operator upgrade successful to 3.11
- quay registry doesn't upgrade
logs from quay operator
{"level":"debug","ts":"2024-03-12T05:02:53Z","logger":"events","msg":"could not inflate kubernetes objects: accumulating resources: accumulation err='accumulating resources from '../../../tmp': cannot read content from non-file ''': recursed accumulation of path 'workspace/kustomize/tmp': accumulating components: loader.New \"'workspace/kustomize/components/pgupgrade/scale-down-clair' doesn't exist\"","type":"Warning","object":{"kind":"QuayRegistry","namespace":"quay-enterprise-14660","name":"quayregistry","uid":"6ebbcfe0-aa4e-430d-97cb-d984fe94d716","apiVersion":"quay.redhat.com/v1","resourceVersion":"117991"},"reason":"ComponentCreationFailed"}
{"level":"info","ts":"2024-03-12T05:02:53Z","msg":"Warning: Reconciler returned both a non-zero result and a non-nil error. The result will always be ignored if the error is non-nil and the non-nil error causes reqeueuing with exponential backoff. For more details, see: https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/reconcile#Reconciler","controller":"quayregistry","controllerGroup":"quay.redhat.com","controllerKind":"QuayRegistry","QuayRegistry":{"name":"quayregistry","namespace":"quay-enterprise-14660"},"namespace":"quay-enterprise-14660","name":"quayregistry","reconcileID":"758dfb59-0095-4bda-8880-f4a780781f43"}
pod status after upgrade
NAME READY STATUS RESTARTS AGE
quay-operator.v3.11.0-6959bb9669-lq6wj 1/1 Running 0 11m
quayregistry-clair-app-8bd49f865-9jx8m 1/1 Running 2 (161m ago) 161m
quayregistry-clair-app-8bd49f865-z6b9c 1/1 Running 0 157m
quayregistry-clair-postgres-7486766546-62p7r 1/1 Running 0 161m
quayregistry-quay-app-5c99d94974-4fn5b 1/1 Running 0 160m
quayregistry-quay-app-5c99d94974-gbzgj 1/1 Running 0 160m
quayregistry-quay-app-upgrade-lvscl 0/1 Completed 0 161m
quayregistry-quay-config-editor-8566f9bf47-s8jgj 1/1 Running 0 161m
quayregistry-quay-database-c6555bd69-s4jsp 1/1 Running 0 158m
quayregistry-quay-mirror-5ccb9dc5cb-rbnxk 1/1 Running 0 161m
quayregistry-quay-mirror-5ccb9dc5cb-xhf9v 1/1 Running 0 161m
quayregistry-quay-redis-75bc44fbd4-6mqpt 1/1 Running 0 161m
Expected Results:
All pods should be upgrade successful
