Bug 1287157

Summary: [RFE] export and import of yum content
Product: Red Hat Satellite 6 Reporter: Chris Duryee <cduryee>
Component: Inter Satellite SyncAssignee: Chris Duryee <cduryee>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: medium    
Version: UnspecifiedCC: bkearney, cduryee, cwelton, jyejare, mmccune, sauchter, xdmoon
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:21:14 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:
Bug Depends On:    
Bug Blocks: 1316897, 950746    

Description Chris Duryee 2015-12-01 16:07:22 UTC
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.

Comment 4 Bryan Kearney 2016-02-15 18:37:33 UTC
*** Bug 1105224 has been marked as a duplicate of this bug. ***

Comment 10 Jitendra Yejare 2016-05-04 06:09:41 UTC
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.

Comment 12 errata-xmlrpc 2016-07-27 09:21:14 UTC
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