-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
quay-v3.16.0
-
False
-
-
False
-
-
Description:
This is an issue found in Quay 3.16.0 Operator, in this new release Quay Operator start to support customized StorageClass, but when give invalid StorageClass, Quay Operator won't validate the StorageClass and start to use invalid StorageClass to deploy Quay, the expected behavior should be Quay Operator stop processing immediately once find the storage Class in invalid, pls review this issue.
Quay:
oc get pod
NAME READY STATUS RESTARTS AGE
quay-operator.v3.16.0-59ddb7bd69-pv6k9 1/1 Running 0 80m
quay316sc-clair-app-68cfbbb888-gzgc7 0/1 CrashLoopBackOff 7 (62s ago) 11m
quay316sc-clair-app-68cfbbb888-sqhsn 0/1 CrashLoopBackOff 7 (51s ago) 11m
quay316sc-clair-app-84ff6fbd6c-fjhxr 0/1 CrashLoopBackOff 5 (2m8s ago) 5m14s
quay316sc-clair-postgres-6697c4c5f9-ghqcd 0/1 Pending 0 5m14s
quay316sc-quay-app-upgrade-ggs57 0/1 CrashLoopBackOff 5 (106s ago) 5m14s
quay316sc-quay-database-576487d4c-z9nkr 0/1 Pending 0 5m14s
quay316sc-quay-mirror-57b469cf48-gwbw4 0/1 Init:CrashLoopBackOff 5 (2m14s ago) 5m13s
quay316sc-quay-mirror-57b469cf48-m2wjk 0/1 Init:CrashLoopBackOff 5 (2m7s ago) 5m13s
quay316sc-quay-redis-766cd74694-d4ln2 1/1 Running 0 5m14s
QuayRegistry CR:
apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quay316sc spec: configBundleSecret: config-bundle-secret components: - kind: objectstorage managed: false - kind: horizontalpodautoscaler managed: true - kind: monitoring managed: false - kind: postgres managed: true overrides: storageClassName: "noquaysc" - kind: clairpostgres managed: true overrides: storageClassName: "noquaysc" - kind: quay managed: true overrides: env: - name: DEBUGLOG value: "true"
Deploy QuayRegistry with invalid StorageClass:
