Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.