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 1726457 - Unable to export content-view that has atleast one non-yum type repo
Summary: Unable to export content-view that has atleast one non-yum type repo
Keywords:
Status: CLOSED DUPLICATE of bug 1671319
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-02 22:04 UTC by Chris Roberts
Modified: 2019-11-27 15:16 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-13 20:07:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris Roberts 2019-07-02 22:04:34 UTC 
Description of problem:
Currently hammer checks all content view repos to see if they are a yum type and if they are not exit out with an error message. We need to be more flexible with the repos so in case a user wants to still export that content view with yum but ignore the other non-yum content

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

Red Hat Satellite 6.5
tfm-rubygem-hammer_cli_katello-0.16.0.11-1.el7sat.noarch


How reproducible:


Steps to Reproduce:
1. Sync a yum repo and create a product/repo of a non-yum type
2. Put that all into a content view and publish
3. Try to export

Actual results:
hammer -u admin content-view version export --id 44  --export-dir /root/

Could not export the content view:
  Error: The Repository 'demo-file' is a non-yum repository. Only Yum is supported at this time. Please remove the repository from the Content View, republish and try the export again.

Expected results:
Have Hammer have the ability to be able to only grab the yum units out of those content views and be more relaxed on the checks

Additional info:
Comment 6 Chris Roberts 2019-09-13 20:07:36 UTC 

*** This bug has been marked as a duplicate of bug 1671319 ***
Note You need to log in before you can comment on or make changes to this bug.