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.

for the stage candlepin2.0, it will always show the name(hostname) in WebUI regardless of the hypervisor_id setting according to "Bug 1458125"

finally, if we set hypervisor_id to uuid, hwuuid, hostname one by one, there are three same hostname items listed in stage webUI for a hypervisor. 

it seems virt-who doesn't need hypervisor_id option any more, sending the hypervisor unique uuid with name is enough. If name changed by customers, virt-who only need to update the display name according to the hypervisor unique uuid, but make sure the unique uuid never be changed.
thus, we are able to keep one entry listed for a hypervisor forever.

Created attachment 1286964 [details]
three same display names for a hypervisor

This is working as designed. When you change the hypervisor_id, the means by which Candlepin uniquely identifies hypervisors, Candlepin will check to see if a consumer exists for that hypervisor_id. On the Candlepin side, we have no way of knowing that this new hypervisor_id refers to the same consumer. As such creating a new consumer is the correct thing to do.