Bug 2191688

Summary:	Unable to use RHEL for VDC subscriptions with hypervisors that are registered to Satellite
Product:	Red Hat Satellite	Reporter:	Jessica Richards <jrichards2>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.12.3	CC:	ahumbe, chrobert, lufu
Target Milestone:	Unspecified	Keywords:	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-14 13:50:48 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 Jessica Richards 2023-04-28 19:50:21 UTC

Description of problem:

When the customer registers a RHEV hypervisor to Satellite, they are unable to use a RHEL for VDC subscription with that hypervisor unless they disable Simple Content Access.  This is a problem because manual subscriptions are slowly being deprecated.


Version-Release number of selected component (if applicable):

Satellite 6.12
hypervisor running either RHEL 7 or RHEL 8

How reproducible:

100%

Steps to Reproduce:
1.  register hypervisor to satellite
2.  install virt-who on the hypervisor as per KCS 1515983
3.  enable simple content access
4.  try to register hosts that live on that hypervisor

Actual results:

Hosts that live on the hypervisor don't receive guest versions of the RHEL for VDC subscription.


Expected results:

Hosts that live on the hypervisor should receive guest versions of the RHEL for VDC subscription.


Additional info:

Maybe we could add a selectable hypervisor option in the Satellite web interface, to hammer, etc.  Just something to tell Satellite that it should prioritize RHEL for VDC subscriptions for that host.

Adding it to the "subscription-manager" command would also be helpful, especially if that were compatible with activation keys.

Comment 1 Brad Buckingham 2023-05-01 13:19:59 UTC

Does this apply only on RHEV hypervisor or also others?

Thanks!

Comment 2 Jessica Richards 2023-05-01 16:10:30 UTC

Brad,

I do not know whether or not this issue arises in other circumstances.  So far I have only observed this issue in a RHEV environment where the hypervisor was registered to the Satellite server.

--
Jessica