6.12. Troubleshooting virt-who

This section lists selected problems that can occur when integrating Satellite with virt-who.
Scenario 1: You have Satellite running together with a hypervisor. You install another hypervisor and run the virt-who command. The host list in the Satellite web UI now displays two green hypervisors. One hypervisor has a subscription attached, and you create a guest ID. Run virt-who again. The host list now displays two green hypervisors, but the new guest ID is displayed as red.
Solution: The hypervisor tool migrated the guest from hypervisor 1 to hypervisor 2. To fix this problem, choose one of the following options:
  • Move the virtual data subscription to hypervisor 2.
  • Move the guest to hypervisor 1.
  • Stop using this guest.
Scenario 2: In Satellite, you provision a guest on a hypervisor that does not have a subscription. The host list in the Satellite web UI displays the hypervisor as yellow. 24 hours later, the hypervisor is displayed as red.
Solution: The hypervisor probably does not have a correctly attached subscription. Obtain a subscription for this hypervisor.
Scenario 3: Either of the following error messages display:
  • Host unknown status
  • Late binding to a host through virt-who (host/guest mapping)
Solution: Search for the error output from virt-who in the /var/log/rhsm/rhsm.log file. Then, search the errors in the knowledgebase in Red Hat Customer Portal.
Scenario 4: In Satellite, you provision a guest on a hypervisor that has a subscription. The host list in the Satellite web UI displays the hypervisor as yellow.
Solution: Either wait for virt-who to run and fix the problem itself, or run virt-who manually.