Bug 2217438

Summary:	Request to fix the documentation about Composite Content View "Repository Restrictions"
Product:	Red Hat Satellite	Reporter:	Sabarinath <sagopina>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED COMPLETED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	bangelic, sajha
Target Milestone:	Unspecified	Keywords:	Documentation, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-17 12:51:53 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:

Description Sabarinath 2023-06-26 09:07:52 UTC

Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/managing_content/index#Composite_Content_Views_Overview_content-management

Section Number and Name: 6.5. Composite Content Views Overview / Repository Restrictions

Describe the issue: As per my testing in my personal labs, I did not hit with this issue and I was able to create 2 component content views, each specifying the same repos "Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8 and Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8" ... and then creating a composite content view that refers to those 2 components. So I think this is no more relevant and needs update.

Suggestions for improvement: Need help to test and fix the issue in the document, so that the customer satellite who is using this method is supported by the SD.

Additional information:

Comment 2 Marie Hornickova 2023-06-27 16:08:13 UTC

Hello Sabarinath,

Thank you for raising this issue for the documentation team. 

The ticket will go through proper team triage, and information about updates on the implementation will be shared in this ticket, as well as the final link to updated product documentation.

Thank you!