Bug 1460607 - one hypervisor, but three same display name in stage candlepin webUI make confused.
one hypervisor, but three same display name in stage candlepin webUI make con...
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who (Show other bugs)
x86_64 Linux
unspecified Severity high
: rc
: ---
Assigned To: Chris Snyder
Depends On:
  Show dependency treegraph
Reported: 2017-06-12 03:55 EDT by Eko
Modified: 2017-06-12 10:12 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-06-12 10:12:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
three same display names for a hypervisor (104.35 KB, image/png)
2017-06-12 03:56 EDT, Eko
no flags Details

  None (edit)
Description Eko 2017-06-12 03:55:27 EDT
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.
Comment 2 Eko 2017-06-12 03:56 EDT
Created attachment 1286964 [details]
three same display names for a hypervisor
Comment 3 Chris Snyder 2017-06-12 10:12:39 EDT
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.

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