Red Hat Bugzilla – Bug 875609
Could not find ESX/Hyper-V host on SAM WebUI
Last modified: 2013-02-21 14:19:21 EST
Description of problem:
After virt-who successfully sending esx/hyper-v hostid:guestids mappings to SAM, we could find the esx host on SAM WebUI. However, we could see the esx guest was associated with the esx host.
Version-Release number of selected component (if applicable):
Step to Reproduce:
1. prepared one rhel6.4 host, and register to SAM:
#subscription-namager register --org=ACME_Corporation --environment=env1
2.Deployed the env of ESX/hyper-v
3.Set the /etc/sysconfig/virt-who on rhel6.4 host
4.Restart virt-who service
#service virt-who restart
5.Log in SAM WebUI and look for esx/hyper-v hosts under "Systems" tab
no esx/hyper-v hosts found
esx/hyper-v hosts found, and can add subscriptions for the esx/hyper-v hosts
Created attachment 647476 [details]
zip file of /var/log/katello
All the files under /var/log/katello are in the zip file, it contains one rhel machine with virt-who running in ESX mode registered to SAM, and both of the two ESX hosts were supposed to register to SAM, but they haven't.
In fixing this issue it was noted that the katello CLI command 'system remove_deletion' does not function correctly. This prevents a hypervisor from being deleted and then re-added again later. A BZ was opened for that regression:
In latest compose
Verified this bug on RHEL6.4-server-x86_64-20121126 + SAM1.2-20121130.n.0 with ESX/Hyper-V and passed.
In SAM WebUI, esx/hyper-v hosts can be found under "Systems" tab, we also have issue mentioned above: https://bugzilla.redhat.com/show_bug.cgi?id=878191.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.