Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 sat6.5-snap20, when setting hypervisor_id=uuid, the entry item of the hypervisor is: virt-who-win-ku00t3htvvh-1
For sat6.5-snap21, when setting hypervisor_id=uuid, the entry item of the hypervisor is: virt-who-564de4d3-9901-f259-6492-7c9a0f296c4b-1
That means this bug(https://bugzilla.redhat.com/show_bug.cgi?id=1408782) is reproduced for sanp21 again.
This was an intended change, see https://bugzilla.redhat.com/show_bug.cgi?id=1687378.
Basically, when you set hypervisor_id=uuid you'd expect the UUID in Katello, not the hostname (as this might be non-unique).
There are two bugs witch are related to this issue.
1. https://bugzilla.redhat.com/show_bug.cgi?id=1693858
This one is for the addition of the fact 'dmi.system.uuid' to the fabrics that have the informton available. This way system can be matched to the current record in candlepin based on that fact and not the hypervisor id that you are meaning to change the value of. Until this issue was filed, it was only available for libvirt and rhevm.
2. https://bugzilla.redhat.com/show_bug.cgi?id=1410601
This is a fix for the candlepin code that allows a hypervisor id change for an existing system.
Marking this bug as dependent on those two.
Eko,
To clarify a bit, https://bugzilla.redhat.com/show_bug.cgi?id=1410601 was never actually fixed for ESX, however behavior in Katello 'masked' that failure and made it appear to work, when in the backend system (candlepin), it never actually was. the issue was that virt-who was not sending up the dmi uuid for esx hypervsisors. This wasn't apparent until katello started basing the host's name off of the hypervisor_id field.
Once virt-who sends up the dmi uuid for esx hypervisors, the behavior desired in 1410601 will return, and Katello will reuse existing host entries no matter what the name is.
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