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.
On the hypervisor JSON data for the hypervisors in VMWare based inventory we are getting blank OS fields:
{
"fqdn": "virt-who-esxi4.lab.eng.rdu2.redhat.com-1",
"account": "540155",
],
"os_release": " ()",
eg:
[root@wallsat67 reports]# cat 4db85b5e-fd5a-4b8b-a4aa-46edaf8bef40.json |json_reformat | grep os_release │········································
"bios_release_date": "12/12/2018", │········································
"os_release": "Red Hat Enterprise Linux Server 7.5 (Maipo)", │········································
"bios_release_date": "09/03/2014", │········································
"os_release": "Red Hat Enterprise Linux Server 7.8 (Maipo)", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"bios_release_date": "12/12/2018", │········································
"os_release": "Red Hat Enterprise Linux Server 7.5 (Maipo)", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"os_release": " ()", │········································
"os_release": " ()",
we are theorizing this may cause hypervisors being dropped on the cloud.redhat.com side after uploading, possibly resulting in miscalculated subscription accounting.
Discovered after filing:
https://bugzilla.redhat.com/show_bug.cgi?id=1884785
os_release is constructed from "distribution::name", "distribution::version" and "distribution::id" host facts. If any field is omitted, "os_release" key will still be present, just missing some data (so you can get values like "Red Hat Enterprise Linux Server 7.9 ()" or " 7.9 (Maipo)"). If all fields are omitted, "os_release" key will not be present at all.
Under normal circumstances, it's not possible to register host with all fields missing to Satellite - Satellite will throw error 500 at subscription-manager when trying to extract major version from "distribution::version" fact.
Tested on:
Satellite 6.9 snap 2
satellite-6.9.0-0.1.beta.el7sat.noarch
pulp-server-2.21.4-1.el7sat.noarch
foreman-2.3.0-0.7.rc2.el7sat.noarch
katello-3.18.0-0.1.rc1.el7sat.noarch
tfm-rubygem-foreman_rh_cloud-2.0.13.1-1.el7sat.noarch
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
On the hypervisor JSON data for the hypervisors in VMWare based inventory we are getting blank OS fields: { "fqdn": "virt-who-esxi4.lab.eng.rdu2.redhat.com-1", "account": "540155", ], "os_release": " ()", eg: [root@wallsat67 reports]# cat 4db85b5e-fd5a-4b8b-a4aa-46edaf8bef40.json |json_reformat | grep os_release │········································ "bios_release_date": "12/12/2018", │········································ "os_release": "Red Hat Enterprise Linux Server 7.5 (Maipo)", │········································ "bios_release_date": "09/03/2014", │········································ "os_release": "Red Hat Enterprise Linux Server 7.8 (Maipo)", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "bios_release_date": "12/12/2018", │········································ "os_release": "Red Hat Enterprise Linux Server 7.5 (Maipo)", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "os_release": " ()", │········································ "os_release": " ()", we are theorizing this may cause hypervisors being dropped on the cloud.redhat.com side after uploading, possibly resulting in miscalculated subscription accounting. Discovered after filing: https://bugzilla.redhat.com/show_bug.cgi?id=1884785