-
Bug
-
Resolution: Not a Bug
-
Critical
-
quay-v3.6.0
-
False
-
False
-
Undefined
-
Description:
This is an issue found when deploy quay with quay 3.6.0 operator using unmanaged route and unmanaged tls components, after create QuayRegistry, found Quay deployment was failed, checked log of Quay Operator POD, get error message "reason": "ConfigInvalid", "message": "required component `route` marked as unmanaged, but `configBundleSecret` is missing necessary fields"}
Note: Quay Operator image is quay-operator-container-v3.6.0-2
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1667063
oc get pod NAME READY STATUS RESTARTS AGE quay360-clair-app-57c785d89c-jmrk2 0/1 CrashLoopBackOff 9 21m quay360-clair-app-57c785d89c-x98jd 0/1 CrashLoopBackOff 9 21m quay360-clair-postgres-74748cddc6-ffbnp 1/1 Running 1 21m quay360-quay-app-upgrade-vv6kp 0/1 Completed 2 21m quay360-quay-config-editor-694ff45cbd-knmqr 1/1 Running 0 21m quay360-quay-database-5f8d7d877d-k7qvb 1/1 Running 0 21m quay360-quay-mirror-86f6ffc449-chf4f 0/1 Init:CrashLoopBackOff 6 21m quay360-quay-mirror-86f6ffc449-jn75k 0/1 Init:CrashLoopBackOff 6 21m quay360-quay-postgres-init-p2t6n 0/1 Completed 0 21m quay360-quay-redis-69c877f9c4-lns6f 1/1 Running 0 21m oc logs quay360-clair-app-57c785d89c-jmrk2 2021/08/02 08:16:56 must provide a -conf flag or set "CLAIR_CONF" in the environment oc get pod quay-operator.v3.6.0-86cbb45f6c-hm47b -n openshift-operators -o json | jq '.spec.containers[0].image' "registry.redhat.io/quay/quay-operator-rhel8@sha256:0d613544009cddf78c1ae8ccd39f082e6304b363244f54bba97afb4b962b4ef1"
Quay Operator POD logs:
2021-08-02T07:55:47.860Z INFO controllers.QuayRegistry finished creating/updating object {"quayregistry": "quay360802", "Name": "quay360-quay-app", "GroupVersionKind": "apps/v1, Kind=Deployment"} 2021-08-02T07:55:48.880Z DEBUG controller-runtime.manager.events Warning {"object": {"kind":"QuayRegistry","namespace":"quay360802","name":"quay360","uid":"d5879ba5-cc92-406c-ba62-8b19cf56d4aa","apiVersion":"quay.redhat.com/v1","resourceVersion":"2418527"}, "reason": "ConfigInvalid", "message": "required component `route` marked as unmanaged, but `configBundleSecret` is missing necessary fields"}
Config.yaml:
DEFAULT_TAG_EXPIRATION: 4w TAG_EXPIRATION_OPTIONS: - 2w - 4w - 8w BROWSER_API_CALLS_XHR_ONLY: false FEATURE_GENERAL_OCI_SUPPORT: true FEATURE_HELM_OCI_SUPPORT: true SUPER_USERS: - quay - admin DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: - default DISTRIBUTED_STORAGE_PREFERENCE: - default DISTRIBUTED_STORAGE_CONFIG: default: - S3Storage - s3_bucket: quay360 storage_path: /quay360 s3_access_key: **** s3_secret_key: ***** host: s3.us-east-2.amazonaws.com
QuayRegistry:
apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quay360 spec: configBundleSecret: config-bundle-secret components: - kind: objectstorage managed: false - kind: route managed: false - kind: tls managed: false
Steps:
- Deploy Quay 3.6.0 Operator to all OCP namespaces
- Create new OCP project named quay360
- Create quay config bundle secret, "oc create secret generic --from-file config.yaml=./config.yaml config-bundle-secret"
- Create QuayRegistry, "oc create -f quayregistry_s3_tls_route_unmanaged.yam"
- Check QuayRegistry status.
https://github.com/quay/enhancements/blob/main/enhancements/tls-managed-component.md
Expected Results:
Quay deployment completed successfully with http traffic.
Actual Results:
Quay deployment was failed.