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:

Currently, Satellite 6 does not support exporting and importing of yum content from content views (both full export/import and incremental). This RFE bz is to track this feature.

Note that this BZ is for the "disconnected" export/import, where an export is written somewhere and then imported elsewhere.

*** Bug 1105224 has been marked as a duplicate of this bug. ***

I verified this feature on Sat 6.2 snaps.

I am able to full export & import and incremental export yum contents from Content view.
But on incremental import of yum contents from exported CV are not updating the packages. So this said incremental import of content view is not working.

Bug https://bugzilla.redhat.com/show_bug.cgi?id=1326852 is already filed and will be fixed in GA.

And so the bug is not currently blocking Beta and as we have separate BZ for incremental import failure, marking this BZ as verified for 3 scenarios full export, full import and incremental export.

Please feel free to reopen if this is not the case.

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/RHBA-2016:1501