Bug 1367838

Summary:	virt-who create additional content hosts consuming twice the number of subscription
Product:	Red Hat Satellite	Reporter:	DzungDo <ddo>
Component:	Subscription Management	Assignee:	Eric Helms <ehelms>
Status:	CLOSED NOTABUG	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	bbuckingham, bkearney, brcoca, egolov, frank.toth, jcallaha, jeanpaul.gatt, jlyle, nshaik, oshtaier, xdmoon, zhunting
Target Milestone:	Unspecified	Keywords:	PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/16205
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-14 16:11:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description DzungDo 2016-08-17 15:23:50 UTC

Description of problem:
virt-who, running in the RHEV environment, creates additional content host for the hypervisor, thus consuming two entitlement instead of 1

Version-Release number of selected component (if applicable):
Satellite 6.2 and possible 6.1

How reproducible:
Always.
As of today, we have 4 outstanding cases in addition to private labs:
01498985 - combination of RHEL-H provisioned by Sat6.1 and virt-who, chews up double licenses
01630978 - [satellite] virt-who causes duplicated entries for virtualisation hosts
01683388 - virt-who creates a duplicate content host for RHEV Hypervisors
01685015 - Multiple licenses being consumed by virt-who and the actual physical host

Steps to Reproduce:
1. install virt-who on Satellite server
2. configure /etc/sysconfig/virt-who and /etc/virt-who.d/somehypervisor.conf
3. start/restart virt-who service on satellite server

Actual results:
virt-who will auto-detect a content host, and would auto-detect type as hypervisor, and name it as virt-who-<hostname>-<org-id> and consume one license. But this content host will remain in "never checked in" status.
In the mean time, in order for the same hypervisor to receive content from Satellite, we need to register it separately, which consume another physical license. But Satellite will not treat the registered content host as a hypervisor, and we would not see any virtual guest associated with host.

Expected results:
Satellite treats the registered content host as a hypervisor.

Additional info:
If we manually registered our rhev host and Satellite treat it as a hypervisor and associate the virtual guests with it, then we can filter out the auto-detected hypervisor and the end result would be only one physical license being consumed.

Or, if virt-who auto-detect the host and we can assign content to this host, then no filtering needed and everyone would be happy with one physical license being consumed.

As of now, virt-who auto-detected the content hosts as the hypervisor and assigns it a different UUID than that of the actual hypervisor.

Comment 2 Zach Huntington-Meath 2016-08-19 17:58:23 UTC

Created redmine issue http://projects.theforeman.org/issues/16205 from this bug

Comment 4 Frank Toth 2017-08-14 07:09:22 UTC

Hi,

Is there any update on this? It is a nightmare with RHEV 4.1 and Satellite 6.2.10
When can we expect the solution?

Thanks,
Frank

Comment 5 Evgeni Golov 2017-08-14 07:29:41 UTC

Could it be that your virt-who is wrongly set up?

See https://access.redhat.com/articles/2884051

For RHV hypervisors that are already subscribed to the Satellite (so called RHEL based hypervisors), you have to run virt-who on the hypervisors (in local/libvirt mode), not on the Satellite (or another host) in vdsm mode.

Comment 6 Frank Toth 2017-08-14 07:44:52 UTC

Hi Evgeni,

Yes, I have to change the config for the RHV hypervisors. Thanks for pointing me to that article. But I have lots of RHEV 3.6 hypervisors which I have to use until I can migrate everything to 4.1.
I think I won't register them to Satellite 6.2 then, just leave them as they are and use virt-who and live with the virt-who-name-ID.

Thanks,
Frank

Comment 10 Bryan Kearney 2017-09-14 16:11:46 UTC

I am closing this out as the issue appears to be resolved. Please let me know if I have closed this out incorrectly.