Bug 1888984

Summary: Hypervisors being reported with number_of_cpus and cores_per_socket == 0
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: RH Cloud - InventoryAssignee: Shimon Shtein <sshtein>
Status: CLOSED ERRATA QA Contact: Mirek Długosz <mzalewsk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: ahumbe, aruzicka, bcourt, cmarinea, egolov
Target Milestone: 6.9.0Keywords: SubscriptionWatch, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_rh_cloud-2.0.13.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1919442 (view as bug list) Environment:
Last Closed: 2021-04-21 13:18:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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