Bug 1937433 - Issues pushing images to Quay using a buildconfig on OpenShift 4.6
Summary: Issues pushing images to Quay using a buildconfig on OpenShift 4.6
Keywords:
Status: CLOSED DUPLICATE of bug 1905095
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Adam Kaplan
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-10 16:23 UTC by Andy Bartlett
Modified: 2024-06-14 00:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-10 19:01:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers image issues 733 0 None closed wrong mediatypes when blob is already present at destination 2021-03-10 16:24:31 UTC

Description Andy Bartlett 2021-03-10 16:23:02 UTC
Description of problem:

Hi,
 I have a customer with the following issue:

Our customers are pushing images to Quay using a buildconfig on OpenShift, they can't define new tags pointing to the same image. Each tag which is pointing to the same image has a different shasum. Another problem is that the size is not shown. 
This is a blocking issue for our team, because they can't see relations between these tags. The workaround which has been mentioned in the case is not an option for us: "That leaves only skopeo copy as a workaround until builders in OpenShift are updated to the new buildah version that does not have bugs indicated earlier."

Our customers do not have rhel hosts with skopeo. I can't copy these tags for them, because it will be a lot of work.

Version-Release number of selected component (if applicable):

Openshift 4.6

How reproducible:

100%


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Adam Kaplan 2021-03-10 19:01:51 UTC
This appears to be the same root issue as Bug #1905095

*** This bug has been marked as a duplicate of bug 1905095 ***


Note You need to log in before you can comment on or make changes to this bug.