Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1692697 - virt-who hypervisor_id has different behaviors between sat6.5-snap20 and sat6.5-snap21 [NEEDINFO]
Summary: virt-who hypervisor_id has different behaviors between sat6.5-snap20 and sat6...
Status: ON_QA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Subscriptions - virt-who
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: 6.5.0
Assignee: William Poteat
QA Contact: Eko
Depends On: 1693858 1694752
TreeView+ depends on / blocked
Reported: 2019-03-26 09:23 UTC by Eko
Modified: 2019-04-12 17:43 UTC (History)
8 users (show)

Fixed In Version: candlepin-2.5.14-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
zhunting: needinfo? (wpoteat)

Attachments (Terms of Use)
sat6.5-snap20 (deleted)
2019-03-26 09:24 UTC, Eko
no flags Details
sat6.5-snap21 (deleted)
2019-03-26 09:24 UTC, Eko
no flags Details

System ID Priority Status Summary Last Updated
Github candlepin candlepin pull 2290 None None None 2019-04-01 15:33:54 UTC

Description Eko 2019-03-26 09:23:33 UTC
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( is reproduced for sanp21 again.

Comment 3 Eko 2019-03-26 09:24:17 UTC
Created attachment 1547968 [details]

Comment 4 Eko 2019-03-26 09:24:40 UTC
Created attachment 1547969 [details]

Comment 5 Evgeni Golov 2019-03-26 09:40:16 UTC
This was an intended change, see

Basically, when you set hypervisor_id=uuid you'd expect the UUID in Katello, not the hostname (as this might be non-unique).

Comment 6 Marek Hulan 2019-03-26 09:59:58 UTC
Eko, please don't use generic WebUI component for things that are specific to some part or page. Thank you

Comment 12 William Poteat 2019-03-29 17:36:57 UTC
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.

Comment 13 Justin Sherrill 2019-04-01 14:22:39 UTC

To clarify a bit,  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.

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