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 1756045 - Unable to export "Default Organization View 1.0" Content View
Summary: Unable to export "Default Organization View 1.0" Content View
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 6.5.3
Assignee: Chris Roberts
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-26 16:38 UTC by Mike McCune
Modified: 2019-10-29 17:22 UTC (History)
12 users (show)

Fixed In Version: tfm-rubygem-hammer_cli_katello-0.16.0.12-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1671319
Environment:
Last Closed: 2019-10-29 17:21:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27187 0 Normal Closed content-view version export fail for "Default Organization View 1.0" 2020-09-25 02:35:55 UTC
Foreman Issue Tracker 27838 0 High Closed Unable to export "Default Organization View 1.0" Content View 2020-09-25 02:35:54 UTC
Github Katello hammer-cli-katello pull 656 0 None closed Fixes #27187 - Fixing Content View version Export for default organiz… 2020-09-25 02:35:59 UTC
Github Katello hammer-cli-katello pull 697 0 None closed Fixes #27838 - Refactor cvv export to allow for default cv 2020-09-25 02:35:59 UTC
Red Hat Product Errata RHBA-2019:3241 0 None None None 2019-10-29 17:22:02 UTC

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
Note You need to log in before you can comment on or make changes to this bug.