Bug 1756045

Summary: Unable to export "Default Organization View 1.0" Content View
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Inter Satellite SyncAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: ahumbe, bkearney, chrobert, dvoss, egolov, ehelms, jcrumple, jyejare, mmccune, trichard, unwosu, vijsingh
Target Milestone: 6.5.3Keywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-hammer_cli_katello-0.16.0.12-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1671319 Environment:
Last Closed: 2019-10-29 17:21:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 6 Jitendra Yejare 2019-10-09 09:41:08 UTC
Verified!

@Satellite 6.5.3


Steps:
-----------
1. Create product and repo with the same name in both exporting and importing orgs.
2. Sync the repo only in exporting org.
3. Export the Default Organization Content View version 1.0 contents from an exporting Org/Satellite.
4. Import the exporting contents from an exported tar from importing Org/Satellite.


Observation:
--------------

Export Succeeds :

# hammer content-view version export --id 89 --export-dir /var/lib/pulp/katello-export/
# ll /var/lib/pulp/katello-export
total 160K
-rw-r--r--. 1 root root 160K Oct  9 05:24 export-5bd79c21-40ab-4cb9-84b2-3d5c9780b8e7-89.tar

Import Succeeds:

# hammer content-view version import --export-tar /var/lib/pulp/katello-export/export-5bd79c21-40ab-4cb9-84b2-3d5c9780b8e7-89.tar --organization-id 11
[.............................................................................................................] [100%]

Comment 8 errata-xmlrpc 2019-10-29 17:21:50 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-2019:3241