Bug 2109365
| Summary: | 'Error reading system DMI information: # SMBIOS implementations newer than version 2.7 are not' when register RHEL-8.7.0-20220718.0 against Satellite6.11 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | qianzhan |
| Component: | subscription-manager | Assignee: | Pino Toscano <ptoscano> |
| Status: | CLOSED ERRATA | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | --- | CC: | jalviso, jsefler, ptoscano, redakkan |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 8.9 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | subscription-manager-1.28.37-1.el8 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-14 15:47:57 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
qianzhan
2022-07-21 04:50:04 UTC
(In reply to qianzhan from comment #0) > Description of problem: > 'Error reading system DMI information: # SMBIOS implementations newer than > version 2.7 are not' when register RHEL-8.7.0-20220718.0 against > Satellite6.11 This is not really an error -- see bug 2035662 for its RHEL 9 equivalent. All we can do in RHEL 8 without backporting the dmidecode rework (bug 2094099), which is not really needed in RHEL 8. This bug also exists on RHEL-8.7.0-20220830.0 against Satellite6.11/Satellite6.12 This issue happens on RHEL-8.8.0-20221120.2 against Satellite6.12. (In reply to Pino Toscano from comment #1) > All we can do in RHEL 8 without backporting the dmidecode rework (bug > 2094099), which is not really needed in RHEL 8. Well, it is actually happening, see bug 2173583, so this will be fixed as by-product of fixing that bug. Also, please note that it has nothing to do with RHEL or Satellite: this comes from the SMBIOS info of the consumer. (In reply to Pino Toscano from comment #4) > (In reply to Pino Toscano from comment #1) > > All we can do in RHEL 8 without backporting the dmidecode rework (bug > > 2094099), which is not really needed in RHEL 8. > > Well, it is actually happening, see bug 2173583, so this will be fixed as > by-product of fixing that bug. > > Also, please note that it has nothing to do with RHEL or Satellite: this > comes from the SMBIOS info of the consumer. Thanks for your update, Pino. (In reply to Pino Toscano from comment #4) > Well, it is actually happening, see bug 2173583, so this will be fixed as > by-product of fixing that bug. To be a bit more specific: the result of the aforementioned bug is that the mentioned warnings are gone. The target release of this bug is 8.9.0, so I will verify it when RHEL8.9-CTC1 comes out. By the way, this bug does not show up when I test RHEL-8.8.0-Beta-1.0 against Satellite6.11/6.12/6.13. (In reply to qianzhan from comment #7) > By the way, this bug does not show up when I test RHEL-8.8.0-Beta-1.0 > against Satellite6.11/6.12/6.13. What matters here is the *system* that is registered: is it a real baremetal system, or a VM? What's the hardware (real or virtual) of that system? (In reply to Pino Toscano from comment #8) > (In reply to qianzhan from comment #7) > > By the way, this bug does not show up when I test RHEL-8.8.0-Beta-1.0 > > against Satellite6.11/6.12/6.13. > > What matters here is the *system* that is registered: is it a real baremetal > system, or a VM? What's the hardware (real or virtual) of that system? Hi, Pino I do not care about the systems provisioned in beaker by CI when I do testing. So I checked the machines that I used to test RHEL-8.8.0-Beta-1.0: kvm-01-guest07.lab.eng.rdu2.redhat.com kvm-01-guest06.lab.eng.rdu2.redhat.com kvm-06-guest07.hv2.lab.eng.bos.redhat.com They are KVM virtual machines. What kind of hardware is needed to verify this bug? The point of this bug is that it entirely depends on the system itself -- it does not even need to be registered, and thus Hosted/Sat/etc does not matter in any way. The quickest way to check for this problem is: - install/provision a RHEL 8 system, without even registering it to Hosted/Stage/Sat - run `subscription-manager facts` to trigger a fact collection - inspect /var/log/rhsm/rhsm.log for the aforementioned "Error reading system DMI information" warning (In reply to qianzhan from comment #10) > What kind of hardware is needed to verify this bug? Unfortunately I don't know whether there is a way to determine the SMBIOS version of a system without accessing to the system itself; on a system, you can easily check the SMBIOS version using the `dmidecode` command (check at the very top of its output) -- for example: # dmidecode | head -n3 # dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 3.2.0 present. To reproduce this bug, the "SMBIOS present" line must have a version greater than 2.7. (In reply to Pino Toscano from comment #11) > The point of this bug is that it entirely depends on the system itself -- it > does not even need to be registered, and thus Hosted/Sat/etc does not matter > in any way. > > The quickest way to check for this problem is: > - install/provision a RHEL 8 system, without even registering it to > Hosted/Stage/Sat > - run `subscription-manager facts` to trigger a fact collection > - inspect /var/log/rhsm/rhsm.log for the aforementioned "Error reading > system DMI information" warning > > (In reply to qianzhan from comment #10) > > What kind of hardware is needed to verify this bug? > > Unfortunately I don't know whether there is a way to determine the SMBIOS > version of a system without accessing to the system itself; on a system, you > can easily check the SMBIOS version using the `dmidecode` command (check at > the very top of its output) -- for example: > > # dmidecode | head -n3 > # dmidecode 3.4 > Getting SMBIOS data from sysfs. > SMBIOS 3.2.0 present. > > To reproduce this bug, the "SMBIOS present" line must have a version greater > than 2.7. Thanks for the details, Pino. It's really helpful to verify 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 (subscription-manager bug fix and enhancement update), 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/RHBA-2023:7092 |