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:
If you create a CV version that only contains non-yum repos, exporting will result in this error:
tar: Cowardly refusing to create an empty archive
Instead, the export should raise a more descriptive error earlier in the process.
Version-Release number of selected component (if applicable):
Satellite 6.5.0
How reproducible:
Steps to Reproduce:
1. Create a content view with only a puppet module
2. Try to export with hammer
3. Get weird error
Actual results:
tar: Cowardly refusing to create an empty archive
Expected results:
Better error message saying why the export failed
Additional info:
This is not supported at the moment so this is just to make a better error message. Should have a PR in for this by Fri 2-29-19 Please triage into 6.5 if I am not in the triage meeting, this was only created upstream hence why it never got flagged for 6.5
Verified!
@ Satellite 6.5 snap 20
Steps:
1. Created Product with puppet repo, having a puppet module
2. Created a Product with above puppet repo.
3. Published above CV
4. Attempted to export above Cv version.
Observation:
1. The non-yum repos(specially are not
# hammer content-view version export --id 3 --export-dir /var/lib/pulp/katello-export
Could not export the content view:
Error: The Content View 'puppet_Cv' contains Puppet modules, this is not supported at this time. Please remove the modules, publish a new version and try the export again.
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, 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/RHSA-2019:1222