Bug 1686964

Summary:	[Modularity] - RHEL 8 Appstream/BaseOS beta Repositories not getting available to the content host.
Product:	Red Hat Satellite	Reporter:	Omkar Khatavkar <okhatavk>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Omkar Khatavkar <okhatavk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	bkearney, csnyder, okhatavk, paji, swadeley
Target Milestone:	6.5.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-14 12:40:24 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 Omkar Khatavkar 2019-03-08 18:34:47 UTC

Description of problem:
RHEL 8 Appstream/BaseOS beta Repositories not getting available to the content host.

Version-Release number of selected component (if applicable):
Satellite 6.5 Snap 18 

How reproducible:
Always 

Steps to Reproduce:
1.Upload the Manifest having RHEL8 beta subscription 
2.Enable the Repos 

Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta Kickstart x86_64
Red Hat Enterprise Linux 8 for x86_64 - AppStream Beta RPMs x86_64
Red Hat Enterprise Linux 8 for x86_64 - BaseOS Beta Kickstart x86_64 
Red Hat Enterprise Linux 8 for x86_64 - BaseOS Beta RPMs x86_64 

3.Sync the Repo
4.Create a content view and activation key 
5.Register Content host. 

Actual results:
Content Host get register but repos are not getting available 
[root@]# subscription-manager repos
This system has no repositories available through subscriptions.

Expected results:
Content Host get register but repos should get available

Additional info:

Comment 14 Omkar Khatavkar 2019-04-01 11:02:16 UTC

Verified with Satellite 6.5 Snap 22, issue not reproducible. Mainly configuration issue.

Comment 17 errata-xmlrpc 2019-05-14 12:40:24 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/RHSA-2019:1222