Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2100759

Summary:	[vCenter] The rhel9.0 guest cannot be associated to the hypervisor in the entitlement server
Product:	Red Hat Enterprise Linux 9	Reporter:	yuefliu <yuefliu>
Component:	virt-who	Assignee:	candlepin-bugs
Status:	CLOSED DUPLICATE	QA Contact:	yuefliu <yuefliu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	hsun, kuhuang, ptoscano, redakkan
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 13:34: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:

Comment 1 Rehana 2022-06-28 13:51:53 UTC

Thanks for the bug Yuefen, Can you please help us with additional details,

1. Please share which guest ids are mapped to which RHEL systems in your observations.
2. Please share the facts output (ex: subscription-manager facts --list) of all the guest system used for this testing (8.6/9.0/9.1) 

Thanks,
Rehana

Comment 4 Pino Toscano 2022-06-30 15:48:26 UTC

Hi yuefliu,

all the rhel9 guests have no DMI facts, and that indeed explains the lack of mapping (since these rhel guests are not reporting any UUID). This is most likely another effect of bug 2094099. To confirm it is indeed the same issue, there are a couple of steps you can check.

The first is: check that the rhel9 guests are in Secure Boot; run `mokutil --sb-state` as root, and if it prints "SecureBoot enabled" it is the case.

In case the rhel9 guests are actually in Secure Boot, try to create a new rhel guest without Secure Boot; in the new VM wizard in vCenter, make sure to unselect it from the hardware details (IIRC it's the last step of the wizard).

If the rhel9 guest without Secure Boot works fine, then it's definitely bug 2094099.