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.
Description of problem:
virt-who is sending the cpu sockets:
~~~
2018-10-12 15:18:34,395 [virtwho.main INFO] MainProcess(1535):Thread-2 @virt.py:_send_data:922 - Report for config "vcenter" gathered, placing in datastore
2018-10-12 15:18:36,552 [virtwho.main INFO] MainProcess(1535):Thread-3 @virt.py:_send_data:922 - Report for config "satotest" gathered, placing in datastore
{
"hypervisors": [
{
"facts": {
"cpu.cpu_socket(s)": "2",
"hypervisor.type": "VMware ESXi",
"hypervisor.version": "6.0.0"
},
~~~
However no sockets are being reported in Satellite:
# curl -s -u $user:$password -k https://$satellite/api/v2/hosts/$host_id/| python -m json.tool | grep "socket(s)"
Sockets count for hypervisor should be included:
https://bugzilla.redhat.com/show_bug.cgi?id=1307024
Version-Release number of selected component (if applicable):
satellite-6.4.0-13.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Setup virt-who to report hypervisors
2. Verify cpu socket count in Satellite
3.
Actual results:
No cpu socket count
Expected results:
see cpu socket count
Additional info:
Description of problem: virt-who is sending the cpu sockets: ~~~ 2018-10-12 15:18:34,395 [virtwho.main INFO] MainProcess(1535):Thread-2 @virt.py:_send_data:922 - Report for config "vcenter" gathered, placing in datastore 2018-10-12 15:18:36,552 [virtwho.main INFO] MainProcess(1535):Thread-3 @virt.py:_send_data:922 - Report for config "satotest" gathered, placing in datastore { "hypervisors": [ { "facts": { "cpu.cpu_socket(s)": "2", "hypervisor.type": "VMware ESXi", "hypervisor.version": "6.0.0" }, ~~~ However no sockets are being reported in Satellite: # curl -s -u $user:$password -k https://$satellite/api/v2/hosts/$host_id/| python -m json.tool | grep "socket(s)" Sockets count for hypervisor should be included: https://bugzilla.redhat.com/show_bug.cgi?id=1307024 Version-Release number of selected component (if applicable): satellite-6.4.0-13.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. Setup virt-who to report hypervisors 2. Verify cpu socket count in Satellite 3. Actual results: No cpu socket count Expected results: see cpu socket count Additional info: