Red Hat Bugzilla – Bug 1004145
Failed to register ESX hypervisor to Stage Candlepin
Last modified: 2016-09-30 10:42:19 EDT
Description of problem:
When running virt-who in ESX mode, an ESX hypervisor host should be registered to Stage Candlepin, so we can register/subscribe ESX host via Stage web UI, thus bonus pool can be shown up in ESX guest, but this ESX host can't be created.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure virt-who in ESX mode, keep virt-who running
2. Register virt-who machine to Stage
3. Check systems in Stage web UI
ESX hypervisor host can not be registered to Stage.
Not only virt-who machine should be registered to Stage, but also an ESX hypervisor host should be registered.
Virt-who manpage says it should always log to /var/log/rhsm/rhsm.log, could we get a copy of this logfile attached to the bug please.
Are we able to get access to ESX that was used? i.e What are the details of virt-who's ESX configuration?
Created attachment 793946 [details]
virt-who log file
Are there any errors that occur after the output of the host/guest mappings? The snippit in the attached log is rather short.
This appears to be an issue in candlepin when multiple systems are running virt-who against the same ESX server.
I believe there is an issue in candlepin's hypervisors API call. The host consumers do not show up b/c another system is running virt-who against the same ESX server and seems to have reported the host/guests first (with a different org). Therefore, the user used in the BZ wouldn't see the hypervisor consumers due to the org that they were initially created in.
Looking at the data in stage, the hypervisor typed consumers for the hosts reported by ESX server appear to have been created against another org.
This boils down to being a configuration issue. Multiple instances of virt-who are configured to report hosts/guests for the same hypervisor instance (vcenter).
We currently do not have multi-tenant support for virt-who instances reporting from the same ESX server. It is out of scope for the upcoming release to add this functionality, so an RFE will be created to address this issue.
Even providing better feedback to virt-who is very hard without being able to uniquely identify the hypervisor instance. Lets address this as part of the RFE.
The restriction of use in current release of Virt-who is inconsistent with ability of subscription services to support multi-tenant (SAM/SAT).