Bug 1664895

Summary:	[RFE] Describe how to export and import content views
Product:	Red Hat Satellite	Reporter:	Andrew Dahms <adahms>
Component:	Documentation	Assignee:	Sergei Petrosian <spetrosi>
Status:	CLOSED NEXTRELEASE	QA Contact:	Melanie Corr <mcorr>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5.0	CC:	chrobert, csherrar, dsinglet, dvoss, jyejare, spetrosi
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-25 09:36:20 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:
Embargoed:
Bug Depends On:	1269273, 1657778
Bug Blocks:

Description Andrew Dahms 2019-01-09 23:38:43 UTC

In Red Hat Satellite 6.5, it is possible to export and import Content Views and Composite Content Views along with their meta data via the API and Hammer. Examples of how to export and import Content Views, along with a brief description of why doing so is helpful to the user, must be added to the Hammer CLI Guide.

Comment 15 Vlada Grosu 2019-02-01 11:11:59 UTC

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

Comment 18 Jitendra Yejare 2019-02-12 07:19:26 UTC

Hi Sergei,

I reviewed the draft and here are my review comments:

Looks like all corrections has been made to the draft and thanks much for doing that.

But, there are some missings from my last comment 7 from section 'anything else customer wants to know about', the missing things are following:
1. About Custom major and minor version - point 2 in comment 7
2. About Mirror-on-sync repos cannot be imported - point 3 in comment 7
3. About composite CVs export/import - point 4 in comment 7

Also,
 
I don't see the https://bugzilla.redhat.com/show_bug.cgi?id=1668544#c7 workaround(just for beta) documented in the draft? Is there a different location to check workarounds in beta docs?

Overall, I see good improvements in Doc. But the missing things are very much required to go in the doc. Please make sure to add them.

Comment 27 Jitendra Yejare 2019-02-12 13:13:16 UTC

Yes Sergie,

I reviewed that and it looks good now.


I was more concerned about the bug https://bugzilla.redhat.com/show_bug.cgi?id=1668544 and what if the customer get that bug during exercising beta.

I wanted to let the customer know that there is some workaround for it https://bugzilla.redhat.com/show_bug.cgi?id=1668544#c7


It seems Dana has already implemented this w/o in Doc as per comment https://bugzilla.redhat.com/show_bug.cgi?id=1668544#c9 and I just wanted to make sure its well documented.

Comment 28 Jitendra Yejare 2019-02-12 13:16:23 UTC

Hello Dana,

Can you please confirm if the documentation for w/o https://bugzilla.redhat.com/show_bug.cgi?id=1668544#c7 is implemented for 6.5 beta? And How can I verify it?

Thanks in advance.

Comment 31 Jitendra Yejare 2019-02-12 14:14:40 UTC

QE - Verified!

Date: Today


As per the discussion above in comments, I have reviewed the updates in the beta document from time to time.

And on reviewing Git Preview in comment 29, I can say the feature CV Export is now well documented and ready to be shipped for Beta(only).

Comment 41 Sergei Petrosian 2019-02-25 09:36:20 UTC

I pushed these changes to master and to 6.5-beta branches.

The updated section resides in the Content Management Guide, section 9. Synchronizing Content Between Satellite Servers.