-
Bug
-
Resolution: Done-Errata
-
Major
-
quay-v3.10.1
-
False
-
None
-
False
-
-
Description of problem:
When set IBM COS as the quay back-end storage, the quay pod can't start for error "The IBMCloudStorage is not a valid storage type".
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.10.1-4 registry.redhat.io/quay/quay-operator-rhel8@sha256:f633b128150edd6c7c7007d37ada82204eef62079811cf0535ab386a73ae1a95 registry.redhat.io/quay/quay-rhel8@sha256:a5d176d8906fd3ef951b16a61dbb246743fead272feddbf2aefc769536367136
How reproducible:
1. configure quay by below config.yaml
DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: - default DISTRIBUTED_STORAGE_PREFERENCE: - default DISTRIBUTED_STORAGE_CONFIG: default: - IBMCloudStorage - s3_bucket: quay3.3.0 storage_path: /quaydata s3_access_key: ****** s3_secret_key: ****** host: s3.us-south.cloud-object-storage.appdomain.cloud
2. start quay deployment
Actual results:
The quay pod can't start by below error message
+------------------------+----------------------------------------------+--------+ | Database | - | 🟢 | +------------------------+----------------------------------------------+--------+ | DistributedStorage | IBMCloudStorage is not a valid storage type. | 🔴 | +------------------------+----------------------------------------------+--------+
Expected results
The quay pod should work correctly with IBMCloudStorage storage type
- links to
-
RHBA-2024:126000
Red Hat Quay v3.10.2 minor release
- mentioned on
