-
Bug
-
Resolution: Done
-
Blocker
-
quay-v3.7.0
Description of problem:
When set "CREATE_PRIVATE_REPO_ON_PUSH: true" and "CREATE_NAMESPACE_ON_PUSH: true", can create no-existing normal organization and repository by podman push successfully, but can not create no-existing repository in user account namespace.
Version-Release number of selected component (if applicable):
quay-operator-bundle-container-v3.7.0-113 Index image v4.8: registry-proxy.engineering.redhat.com/rh-osbs/iib:227057 quay-operator-rhel8@sha256:b8969f8586d7f48001630d3824ed8a4d845139667eb074fec4ec6582562619ef
How reproducible:
always
Steps to Reproduce:
1. Create a user, such as whuquay
2. set "CREATE_PRIVATE_REPO_ON_PUSH: true" and "CREATE_NAMESPACE_ON_PUSH: true" in config.yaml
...... SUPER_USERS: - whuquay - whutest FEATURE_ANONYMOUS_ACCESS: true FEATURE_QUOTA_MANAGEMENT: true FEATURE_PROXY_CACHE: true BROWSER_API_CALLS_XHR_ONLY: false CREATE_PRIVATE_REPO_ON_PUSH: true CREATE_NAMESPACE_ON_PUSH: true FEATURE_USERNAME_CONFIRMATION: false FEATURE_USER_INITIALIZE: true .....
3. deploy quay and login quay with user "whuquay".
4. push image to "whuquay" namespace with "noexist" repository by podman
$ podman push --tls-verify=false quayregistry-quay-quay-enterprise.apps.whu48az13.qe.azure.devcluster.openshift.com/whuquay/noexist:ppc64le Getting image source signatures Error: Error copying image to the remote destination: Error trying to reuse blob sha256:1ec79c72d048427efba9e9f8cdb832fd7b4d8edd8c2cd3047695822ffce11c19 at destination: unexpected http code: 405 (Method Not Allowed), URL: https://quayregistry-quay-quay-enterprise.apps.whu48az13.qe.azure.devcluster.openshift.com/v2/auth?account=whuquay&scope=repository%3Awhuquay%2Fnoexist%3Apull%2Cpush&service=quayregistry-quay-quay-enterprise.apps.whu48az13.qe.azure.devcluster.openshift.com
Actual results:
Got error message and failed to push image to no-existing repository in user account namespace. repush image still failed.
Expected results:
Podman push operation can trigger no-existing repository creation successfully and the image is pushed successfully.
Additional info:
Only hit this issue in user account namespace. for normal organization, podman push operation can trigger no-existing normal organization and no-existing repository creation successfully.
$ podman push --tls-verify=false quayregistry-quay-quay-enterprise.apps.whu48az13.qe.azure.devcluster.openshift.com/noexist_org/noexist_repo:ppc64le Getting image source signatures Copying blob 1ec79c72d048 [--------------------------------------] 0.0b / 0.0b Copying config 9c3181779a done Writing manifest to image destination Storing signatures $ podman push --tls-verify=false quayregistry-quay-quay-enterprise.apps.whu48az13.qe.azure.devcluster.openshift.com/exist_org/noexist_repo:ppc64le Getting image source signatures Copying blob 1ec79c72d048 [--------------------------------------] 0.0b / 0.0b Copying config 9c3181779a done Writing manifest to image destination Storing signatures
$ oc get pod NAME READY STATUS RESTARTS AGE .... quayregistry-quay-app-857bbd54b7-dgjdh 1/1 Running 0 126m quayregistry-quay-app-857bbd54b7-mbtbf 1/1 Running 0 125m ......
The attachment includes the quay pods logs
- is cloned by
-
-
- Closed
-
