Bug 1399879 - Exporting Content View Versions (CVVs) to a Directory in APPENDIX C. SYNCHRONIZING CONTENT BETWEEN SATELLITE SERVERS
Summary: Exporting Content View Versions (CVVs) to a Directory in APPENDIX C. SYNCHRON...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Content Management Guide
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
low vote
Target Milestone: Unspecified
Assignee: Zac Dover
QA Contact: Lucie Jirakova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-30 00:56 UTC by Dustin Boyd
Modified: 2019-09-26 14:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-24 12:46:55 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dustin Boyd 2016-11-30 00:56:01 UTC
Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/content-management-guide/appendix-c-synchronizing-content-between-satellite-servers

Section Number and Name: C.6.2. "Exporting Content View Versions (CVVs) to a Directory"

Describe the issue: Missing information on Organization-Default_Organization_View-v1.0 under "To Determine Which Content View Version to Export:"

Suggestions for improvement: 
In section C.6.2. "Exporting Content View Versions (CVVs) to a Directory" under "To Determine Which Content View Version to Export:" the output on my customer's system notes a "Organization-Default_Organization_View-v1.0" as the content view to be exported for his configuration without a need to publish or promote additional content views. He is using 'hammer content-view version list --organization "Organization_Name" ' instead of the noted 'hammer content-view version list --organization "Mega Corporation" --content-view cdn.megacorp.com ' command to see the "Organization-Default_Organization_View-v1.0" for his proper export/import from connected to disconnected Satellite.

Additional information: Comment on access.redhat.com already for customer to approve ticket closure.

Comment 1 Andrew Dahms 2017-01-23 04:06:05 UTC
Assigning to Zac for review.

Zac - based on the comment above, it looks like all we need is to update the command in section C.6.2 to the following recommended command:

hammer content-view version list --organization "Organization_Name"

Comment 6 Andrew Dahms 2017-01-24 12:46:55 UTC
This content is live on the Customer Portal.

Closing.


Note You need to log in before you can comment on or make changes to this bug.