While attempting to use a subscription (Red Hat Enterprise Linux Server, Premium (1-2 sockets) (Unlimited guests)) in an ESXi environment, it seems virt-who is creating hypervisor accounts instead of the guests in katello. vsphere.py has applied the changes from https://git.fedorahosted.org/cgit/virt-who.git/commit/?id=543ba2d983c8588b568664237488d16401253b58 virt-who is running on the katello server which is registered to itself using subscription-manager.
virt-who doesn't create any accounts, it merely reports association between virtualization hosts and their guests.
Perhaps you can answer something for me about how I should be using virt-who, then. It has obviously picked up several hosts, but when I register another server to Katello it doesn't find the host that the server is on. It recognizes that the system is a guest, but can't find the host. Is this because I'm using ESXi? Any direction would be greatly appreciated.
It might be bug in virt-who. Could you check logs in /var/lib/rhsm.log if the host-guest association is obtained correctly (or attach the log file here or send it to me to rnovacek (at) redhat (dot) com). You might need to set VIRTWHO_DEBUG=1 in /etc/sysconfig/virt-who.
Created attachment 790992 [details] rhsm.log This log starts at the point where I was able to get virt-who to connect to vcenter.
The log is quite silent about virt-who, could you enable the debug mode as I suggested in comment #3.
Created attachment 791132 [details] rhsm with virt-who debug set
It seems that you're facing bug 1002058. When there is a lot of virtual guests (more than 100), virt-who fails to report their UUIDs correctly.
I installed the latest version from git repo (as of about 3PM EST), however I now get errors in rhsm.log (attached)
Created attachment 791520 [details] rhsm with update after bugfix
This can be closed, by the way. The version of virt-who from 2013-08-30 has solved this.
See comment 9.