Bug 2250237

Summary:	"hammer repository upload-content" not long working for docker repository
Product:	Red Hat Satellite	Reporter:	Hao Chang Yu <hyu>
Component:	Container Management - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.6	CC:	ahumbe, iballou, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:36:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.