Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
On some of the RHEL7.4 supported arches (aarch64, ppc64le, ppc64, s390x) (but NOT x86_64) dmidecode warnings like the following are being printed to stderr for many subscription-manager calls.
** COLLECTED WARNINGS **
/sys/firmware/efi/systab: SMBIOS entry point missing
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **
This is a regression from subscription-manager-1.17 behavior on RHEL7.3 and is causing many automated test failures due to the unexpected stderr messages.
Version-Release number of selected component (if applicable):
[root@hp-moonshot-03-c36 ~]# rpm -q subscription-manager python-rhsm
subscription-manager-1.19.4-1.el7.aarch64
python-rhsm-1.19.2-1.el7.aarch64
[root@hp-moonshot-03-c36 ~]# rpm -qa | grep dmidecode
python-dmidecode-3.12.2-1.el7.aarch64
dmidecode-3.0-4.el7.aarch64
How reproducible:
Steps to Reproduce:
Use Beaker to reserve a RHEL74 aarch64, ppc64le, ppc64, s390x system, then run a subscription-manager command (e.g. subscription-manager version) and you will see unexpected warnings print to stderr...
HERE'S A FAILURE ON aarch64
[root@hp-moonshot-03-c36 ~]# uname -m
aarch64
[root@hp-moonshot-03-c36 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
subscription-manager: 1.19.4-1.el7
python-rhsm: 1.19.2-1.el7
** COLLECTED WARNINGS **
/sys/firmware/efi/systab: SMBIOS entry point missing
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **
[root@hp-moonshot-03-c36 ~]#
HERE'S A FAILURE ON ppc64le
[root@ibm-p8-05-lp2 ~]# uname -m
ppc64le
[root@ibm-p8-05-lp2 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
subscription-manager: 1.19.4-1.el7
python-rhsm: 1.19.2-1.el7
** COLLECTED WARNINGS **
/dev/mem (mmap): Operation not permitted
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **
[root@ibm-p8-05-lp2 ~]#
Actual results:
above
Expected results:
should not print list of ** COLLECTED WARNINGS ** / ** END OF WARNINGS **
Additional info:
Preliminary troubleshooting indicates that subscription-manager's dmiinfo code previously called dmidecode.clear_warnings() which probably suppressed printing of the COLLECTED WARNINGS. These recent dbus pull requests are likely candidates that introduced this regression in behavior...
https://github.com/candlepin/subscription-manager/pull/1509https://github.com/candlepin/subscription-manager/pull/1543
Note: Despite the unexpected list of COLLECTED WARNINGS being printed to stderr, the subscription-manager modules are functioning well. A consumer can still register and attach subscriptions.
Retested with :
# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
subscription-manager: 1.19.8-1.el7
python-rhsm: 1.19.5-1.el7
** COLLECTED WARNINGS **
/sys/firmware/efi/systab: SMBIOS entry point missing
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **
[root@hp-moonshot-03-c37 ~]# uname -m
aarch64
I still see the warning messages
Reproduced the failure on RHEL 74 (RHEL-7.4-20170420.n.0)
on aarch64:
[root@hp-moonshot-03-c13 ~]# uname -m
aarch64
[root@hp-moonshot-03-c13 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
subscription-manager: 1.19.8-1.el7
python-rhsm: 1.19.5-1.el7
** COLLECTED WARNINGS **
/sys/firmware/efi/systab: SMBIOS entry point missing
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **
on s390x :
[root@ibm-z-66 ~]# uname -m
s390x
[root@ibm-z-66 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
subscription-manager: 1.19.8-1.el7
python-rhsm: 1.19.5-1.el7
** COLLECTED WARNINGS **
/dev/mem (mmap): Operation not permitted
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **
Unable to get ppc64le and ppc64 machines from beaker as the request gets aborted. Based on the 2 failures above (on aarch64 and s390x) moving the bug to New
Comment 11Gustavo Luiz Duarte (IBM)
2017-04-20 19:49:51 UTC
*** Bug 1443915 has been marked as a duplicate of this bug. ***
Comment 12Gustavo Luiz Duarte (IBM)
2017-04-20 19:54:46 UTC
*** Bug 1443277 has been marked as a duplicate of this bug. ***
This issue was resolved in automated testruns for all arches of RHEL-7.4-Alpha-1.0 compose RHEL-7.4-20170421.1 with subscription-manager-1.19.9-1.el7
Moving to VERIFIED
------- Comment From hannsj_uhl.com 2017-05-11 03:36 EDT-------
Comment from Harish Sriram 2017-05-10 23:49:12 CDT
Issue is not observed with latest release
# subscription-manager version
subscription-manager: 1.19.12-1.el7
python-rhsm: 1.19.6-1.el7
# uname -a
Linux ltc-garri1.aus.stglabs.ibm.com 4.11.0-1.el7.ppc64le #1 SMP Wed May 3 18:32:58 EDT 2017 ppc64le ppc64le ppc64le GNU/Linux
Comment 17Hanns-Joachim Uhl
2017-05-11 07:46:15 UTC
oops ... the previous comment has to read:
"
Issue is not observed with latest release
# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
subscription-manager: 1.19.12-1.el7
python-rhsm: 1.19.6-1.el7
# uname -a
Linux ltc-garri1.aus.stglabs.ibm.com 4.11.0-1.el7.ppc64le #1 SMP Wed May 3
18:32:58 EDT 2017 ppc64le ppc64le ppc64le GNU/Linux
"
...
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, 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-2017:2083