Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Docker images can not be exported from satellite either as repository or as part of CV to be used in disconnected satellite.
Version-Release number of selected component (if applicable):
6.4
6.3
How reproducible:
1. Create a custom product & create repository of docker type.
2. Sync the repository.
3. Export the docker images as repository gives below error.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@satellite ~]# hammer repository export --id 2
Could not export the repository:
Repository content type must be 'yum' to export.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
4. Export it as part of CV gives below error.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@vm249-255 ~]# hammer content-view version export --id 2
[.........................................................................................................................................] [100%]
Error: No such file or directory @ rb_file_s_stat - /var/lib/pulp/published/yum/master/group_export_distributor/RedOrg-opencv-v1.0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Steps to Reproduce:
1. Create a custom product & create repository of docker type.
2. Sync the repository.
3. Export the docker images as repository gives below error.
4. Export it as part of CV gives below error.
Actual results:
Export as repository or part of CV fails with error.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@satellite ~]# hammer repository export --id 2
Could not export the repository:
Repository content type must be 'yum' to export.
++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[root@vm249-255 ~]# hammer content-view version export --id 2
[.........................................................................................................................................] [100%]
Error: No such file or directory @ rb_file_s_stat - /var/lib/pulp/published/yum/master/group_export_distributor/RedOrg-opencv-v1.0
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Expected results:
Docker images should be exported either as repository or as Part of CV
Additional info:
Same behaviour has been observed in
satellite 6.3
satellite 6.4
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Satellite 6.12.5 Async Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:4749