Bug 1888984 - Hypervisors being reported with number_of_cpus and cores_per_socket == 0
Summary: Hypervisors being reported with number_of_cpus and cores_per_socket == 0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Inventory
Version: 6.6.0
Hardware: All
OS: All
unspecified
high
Target Milestone: 6.9.0
Assignee: Shimon Shtein
QA Contact: Mirek Długosz
URL:
Whiteboard:
: 1893209 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-16 17:00 UTC by Waldirio M Pinheiro
Modified: 2024-03-25 16:45 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman_rh_cloud-2.0.13.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1919442 (view as bug list)
Environment:
Last Closed: 2021-04-21 13:18:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:18:42 UTC

Description Waldirio M Pinheiro 2020-10-16 17:00:44 UTC
Description of problem:
Virt-who is collecting the information correctly from vCenter, however, rh_cloud plugin is generating the information as we can see below
---
            "system_profile": {
                "number_of_cpus": 0,		<<<<<<<<<<<<<<<<<<<<<<<<<
                "number_of_sockets": 2,
                "cores_per_socket": 0,		<<<<<<<<<<<<<<<<<<<<<<<<<
                "system_memory_bytes": 0,
---

As consequence, this will cause erros on subscription watch.

Version-Release number of selected component (if applicable):
6.6 and 6.7

How reproducible:
100%

Steps to Reproduce:
1. Install rh_cloud plugin
2. Generate a new report
3. Check the generated json files and confirm if there are machines with number_of_cpus == 0 and/or cores_per_socket == 0

Actual results:
Some json reports are presenting this behavior

Expected results:
The information be correct, once the virt-who will report only "cpu.cpu_socket(s)"

Additional info:

Comment 6 Shimon Shtein 2020-11-10 13:08:50 UTC
*** Bug 1893209 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2021-04-21 13:18:20 UTC
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 (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1313


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