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:
This is a regression in behavior... The offending subscription-manager commit is f27dafb75bc8a2e20bd8ded0414344ea7b5eade9
Version-Release number of selected component (if applicable):
[root@jsefler-rhel7 ~]# rpm -q subscription-manager python-rhsm
subscription-manager-1.19.8-1.el7.x86_64
python-rhsm-1.19.5-1.el7.x86_64
How reproducible:
Steps to Reproduce:
[root@jsefler-rhel7 ~]# echo '{"system.certificate_version":"1.0"}' > /etc/rhsm/facts/custom.facts
[root@jsefler-rhel7 ~]# subscription-manager facts | grep certificate_version
system.certificate_version: 3.2
Actual results:
system.certificate_version: 3.2
Expected results:
system.certificate_version: 1.0
Additional info:
This does not affect all facts. For example, a custom fact for "cpu.cpu_socket(s)" is working as expected...
[root@jsefler-rhel7 ~]# subscription-manager facts | grep cpu.cpu_socket
cpu.cpu_socket(s): 2
[root@jsefler-rhel7 ~]# echo '{"cpu.cpu_socket(s)":"1"}' > /etc/rhsm/facts/custom.facts
[root@jsefler-rhel7 ~]# subscription-manager facts | grep cpu.cpu_socket
cpu.cpu_socket(s): 1
I can confirm this behavior in master too. Output from /var/log/rhsm/rhsm.log in upstream version shows that subscription-manager reads custom.facts twice:
2017-04-24 21:42:47,515 [INFO] subscription-manager:3061:MainThread @custom.py:85 - Loading custom facts from: /etc/rhsm/facts/custom.facts
2017-04-24 21:42:47,522 [INFO] subscription-manager:3061:MainThread @custom.py:85 - Loading custom facts from: /etc/rhsm/facts/custom.facts
but subscription-manager (version 1.17.15) reads it only once.
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
Description of problem: This is a regression in behavior... The offending subscription-manager commit is f27dafb75bc8a2e20bd8ded0414344ea7b5eade9 Version-Release number of selected component (if applicable): [root@jsefler-rhel7 ~]# rpm -q subscription-manager python-rhsm subscription-manager-1.19.8-1.el7.x86_64 python-rhsm-1.19.5-1.el7.x86_64 How reproducible: Steps to Reproduce: [root@jsefler-rhel7 ~]# echo '{"system.certificate_version":"1.0"}' > /etc/rhsm/facts/custom.facts [root@jsefler-rhel7 ~]# subscription-manager facts | grep certificate_version system.certificate_version: 3.2 Actual results: system.certificate_version: 3.2 Expected results: system.certificate_version: 1.0 Additional info: This does not affect all facts. For example, a custom fact for "cpu.cpu_socket(s)" is working as expected... [root@jsefler-rhel7 ~]# subscription-manager facts | grep cpu.cpu_socket cpu.cpu_socket(s): 2 [root@jsefler-rhel7 ~]# echo '{"cpu.cpu_socket(s)":"1"}' > /etc/rhsm/facts/custom.facts [root@jsefler-rhel7 ~]# subscription-manager facts | grep cpu.cpu_socket cpu.cpu_socket(s): 1