Bug 1001306 - virt-who creates hypervisor instead of guest
Summary: virt-who creates hypervisor instead of guest
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Radek Novacek
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
 
Reported: 2013-08-26 20:59 UTC by robert.redhat
Modified: 2019-09-26 13:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-05 18:03:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhsm.log (38.69 KB, text/plain)
2013-08-27 14:10 UTC, robert.redhat
no flags Details
rhsm with virt-who debug set (8.96 KB, text/plain)
2013-08-27 17:51 UTC, robert.redhat
no flags Details
rhsm with update after bugfix (3.47 KB, text/plain)
2013-08-28 19:38 UTC, robert.redhat
no flags Details

Description robert.redhat 2013-08-26 20:59:11 UTC
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.

Comment 1 Radek Novacek 2013-08-27 06:58:11 UTC
virt-who doesn't create any accounts, it merely reports association between virtualization hosts and their guests.

Comment 2 robert.redhat 2013-08-27 12:24:23 UTC
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.

Comment 3 Radek Novacek 2013-08-27 12:40:49 UTC
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.

Comment 4 robert.redhat 2013-08-27 14:10:55 UTC
Created attachment 790992 [details]
rhsm.log

This log starts at the point where I was able to get virt-who to connect to vcenter.

Comment 5 Radek Novacek 2013-08-27 14:37:10 UTC
The log is quite silent about virt-who, could you enable the debug mode as I suggested in comment #3.

Comment 6 robert.redhat 2013-08-27 17:51:52 UTC
Created attachment 791132 [details]
rhsm with virt-who debug set

Comment 7 Radek Novacek 2013-08-28 14:38:33 UTC
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.

Comment 8 robert.redhat 2013-08-28 19:37:01 UTC
I installed the latest version from git repo (as of about 3PM EST), however I now get errors in rhsm.log (attached)

Comment 9 robert.redhat 2013-08-28 19:38:00 UTC
Created attachment 791520 [details]
rhsm with update after bugfix

Comment 10 robert.redhat 2013-09-05 18:02:30 UTC
This can be closed, by the way. The version of virt-who from 2013-08-30 has solved this.

Comment 11 Bryan Kearney 2013-09-05 18:03:55 UTC
See comment 9.


Note You need to log in before you can comment on or make changes to this bug.