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.
Created attachment 1547968 [details]
Created attachment 1547969 [details]
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).
Eko, please don't use generic WebUI component for things that are specific to some part or page. Thank you
There are two bugs witch are related to this issue.
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.
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.
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.
No, there should be one entry. The actual displayed name is up to Satelite.
You need a newer version of virt-who for this to happen: 0.24.4-1
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.