Hypervisors are reported to Red Hat Satellite 6 with UUID when hostname based reporting is configured.
Environment
- Red Hat Satellite 6.x
- Virt-who
Issue
- Virt-who profiles of the hypervisors on Red Hat Satellite 6 are created with UUID even when hypervisor_id on the virt-who configuration is set to hostname.
Resolution
-
Find all the virt-who services reporting to the Satellite. Execute the following command on the Satellite CLI to find the IP address of all the virt-who service hosting servers reporting to the Satellite:
# grep -i "cmd=virt-who" /var/log/httpd/foreman-ssl_access_ssl.log | awk '{print $1}'| sort -u -
Confirm there are no duplicate configurations for the same server on all the virt-who servers. Execute the following command on the servers hosting the virt-who service to find the server name.
# grep server /etc/virt-who.d/* -
Make sure that all of the configurations are reporting using hostname instead of UUID:
[virt-who-config-X] type=hyperv hypervisor_id=hostname <------------- owner=Organization env=Library server=vcenter.example.com username=username\domain encrypted_password=<VCenterPassword> rhsm_hostname=satellite.example.com rhsm_username=<VirtWhoReporter> rhsm_encrypted_password=<SatelliteVirtWhoReporterPassword> rhsm_prefix=/rhsm
For more KB articles/solutions related to Virt-who and Virtual Datacenter (VDC) Subscriptions Issues, please refer to the Consolidated Troubleshooting Article for Virt-who and Virtual Datacenter (VDC) Subscriptions Issues
Root Cause
- Multiple virt-who services were reporting to the Satellite for the same server of which a few were using UUID for hypervisor_id in the configuration.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.