-
Bug
-
Resolution: Done
-
Critical
-
quay-v3.6.4
Description of problem:
When set CREATE_NAMESPACE_ON_PUSH: true, make sure existing image repos in quay do not contain the same layer with pushing images, push image to non-existing org and repo. The org and repo are created, but pushing is failed
Version-Release number of selected component (if applicable):
$ skopeo --version
skopeo version 1.5.1
How reproducible:
Steps to Reproduce:
1. set CREATE_NAMESPACE_ON_PUSH: true in config.yaml
2. make sure existing image repos in quay do not contain the same layer with pushing images
3. push image to non-existing org and repo
Actual results:
The org and repo are created, but pushing is failed
$ skopeo copy --dest-creds=root:quayroot --dest-tls-verify=false docker://quay.io/projectquay/clair:4.1.2 docker://example-quay-quay36.router-default.apps.dyan89.qe.devcluster.openshift.com/clair/clair
Getting image source signatures
Copying blob a3ba00ce78fe done
FATA[0001] Error trying to reuse blob sha256:158b4527561fa6bd9dc89217fff5b1f4cce16fdc5a5aef36345db0554ba996fc at destination: Requesting bear token: invalid status code from registry 405 (Method Not Allowed)
Expected results:
succeed
Additional info:
when re-push the same image to same repo, pushing is succeed
- account is impacted by
-
PROJQUAY-3867 Update OMR to use 3.7.0 Quay image
- Closed
- blocks
-
PROJQUAY-1928 As a simple registry user, I want push to non-existent org to create the org, for convenience.
- Closed
- relates to
-
PROJQUAY-3998 First push of an image to a mirror registry fails
- Closed