-
Bug
-
Resolution: Done
-
Major
-
quay-v3.12.1
-
False
-
None
-
False
-
-
Description:
This is an issue found in Quay 3.12.1, with new config "signature_version: v4", when configured Quay with Hitachi HCP CS Storage, pull image hit error "Error: parsing image configuration: fetching blob: StatusCode: 403, "<?xml version='1.0' encoding='UTF-8'?><Error><Code..."", pls review this issue, see attached Quay App Pod logs quay3121_quay_app_pod1.logs
and quay3121_quay_app_pod2.logs
Clair App Pod Logs: quay3121_hitachi_clair_app_pod.logs
Quay: 3.12.1 with latest build quay-operator-bundle-container-v3.12.1-13
podman pull quay3121hitachi-quay-quay3121.apps.quaytest-2954.qe.devcluster.openshift.com/qateam/demo:debian --tls-verify=false Trying to pull quay3121hitachi-quay-quay3121.apps.quaytest-2954.qe.devcluster.openshift.com/qateam/demo:debian... Error: parsing image configuration: fetching blob: StatusCode: 403, "<?xml version='1.0' encoding='UTF-8'?><Error><Code..."
Quay Config.yaml:
DEFAULT_TAG_EXPIRATION: 2w
DISTRIBUTED_STORAGE_CONFIG:
local_us:
- RadosGWStorage
- access_key: ******
bucket_name: quay3121rados
hostname: tryhcpforcloudscale.hitachivantara.com
is_secure: true
port: "443"
secret_key: ******
storage_path: /datastorage/registry
signature_version: v4
DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS:
- local_us
DISTRIBUTED_STORAGE_PREFERENCE:
- local_us
PERMANENTLY_DELETE_TAGS: true
RESET_CHILD_MANIFEST_EXPIRATION: true
FEATURE_EXTENDED_REPOSITORY_NAMES: true
CREATE_NAMESPACE_ON_PUSH: true
FEATURE_QUOTA_MANAGEMENT: true
FEATURE_PROXY_CACHE: true
FEATURE_USER_INITIALIZE: true
FEATURE_PROXY_STORAGE: true
FEATURE_UI_V2: true
FEATURE_SUPERUSERS_FULL_ACCESS: true
FEATURE_AUTO_PRUNE: true
