This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2250237 - "hammer repository upload-content" not long working for docker repository
Summary: "hammer repository upload-content" not long working for docker repository
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management - Content
Version: 6.13.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-11-17 08:06 UTC by Hao Chang Yu
Modified: 2024-06-06 16:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:36:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-21359 0 None Migrated None 2024-06-06 16:36:31 UTC

Description Hao Chang Yu 2023-11-17 08:06:10 UTC 
Description of problem:
We upload different images to each docker repositories but all the docker repositories ended up associating to the same manifest list and/or manifests. The associating manifest list/manifests are not belonged to any of the uploaded docker images.


How reproducible:
Easy


Steps to Reproduce:
1. Sync any repository from upstream docker registry so that the Satellite will have some existing docker manifests.
2. Follow KCS "https://access.redhat.com/solutions/4175551" to prepare multiple docker image tarball using skopeo.  
3. Create a docker repository for each of the image and upload the tarball using the following commands
~~~
hammer repository create --product <product> --organization <organization> --name <repository name> --content-type docker
hammer repository upload-content --name <repository name>  --organization <organization> --product <product> --path /<path>/<to>/<image tarball>/<image name>.tar
~~~

Actual results:
Upload commands completed successfully but if we use the following command to check the repository manifest, we will found that they are all associating to the same manifests.
~~~
hammer docker manifest list --repository  <repository name> --organization <organization> --product <product>
~~~

Expected results:
Upload works correctly.


Additional info:

It appears that the upload-content is not implemented to support Pulp3 container plugin.
Comment 9 Ian Ballou 2023-12-13 21:37:20 UTC 
This BZ will be used to halt uploading content to container repositories while 'container push' is being developed. That will be the feature that enables "uploading" container content (https://bugzilla.redhat.com/show_bug.cgi?id=1313502).
Comment 10 Eric Helms 2024-06-06 16:36:33 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.