Bug 2191688 - Unable to use RHEL for VDC subscriptions with hypervisors that are registered to Satellite
Summary: Unable to use RHEL for VDC subscriptions with hypervisors that are registered...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.12.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-28 19:50 UTC by Jessica Richards
Modified: 2023-08-14 13:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 13:50:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-17426 0 None None None 2023-05-01 16:12:19 UTC
Red Hat Knowledge Base (Solution) 1515983 0 None None None 2023-04-28 19:50:20 UTC

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


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