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 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:

*** Bug 1893209 has been marked as a duplicate of this bug. ***

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