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.
Demonstrating the original failure on a RHEL8.2 system that has been upgraded (not shown) from RHEL8.1 can result in the absence of a processTimeout configuration which can cause the follow issue...
[root@ibm-x3650m4-01-vm-14 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.2 (Ootpa)
[root@ibm-x3650m4-01-vm-14 ~]# rpm -q subscription-manager
subscription-manager-1.26.16-1.el8.x86_64
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# grep --ignore-case "processTimeout" /etc/rhsm/rhsm.conf
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# subscription-manager config | grep --ignore-case "processTimeout"
processtimeout = [300]
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# subscription-manager config --rhsmd.processtimeout=120
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# subscription-manager config | grep --ignore-case "processTimeout"
processtimeout = 120
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# grep --ignore-case "processTimeout" /etc/rhsm/rhsm.conf
processtimeout = 120
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# time /etc/cron.daily/rhsmd
real 5m0.056s <========== PROCESS TIMEDOUT AFTER 300 SECONDS, NOT 120 AS EXPECTED
user 0m0.610s
sys 0m0.120s
BANG! Although we correctly used subscription-manager config tool to change the value of the default "processtimeout" value (from 300 seconds) to a different value (120 seconds) the new configuration was not honored and the actual time it took /etc/cron.daily/rhsmd to timeout was 5 minutes (equal to the default 300 seconds)..
Now I will upgrade (not shown) subscription-manager to the fixed version and re-test...
[root@ibm-x3650m4-01-vm-14 ~]# rpm -q subscription-manager
subscription-manager-1.26.17-1.el8_2.x86_64
[root@ibm-x3650m4-01-vm-14 ~]# rpm -q subscription-manager --changelog | grep 1828657
- 1828657: Make rhsmd cron read 'processTimeout' case-insensitive
[root@ibm-x3650m4-01-vm-14 ~]#
[root@ibm-x3650m4-01-vm-14 ~]# grep --ignore-case "processTimeout" /etc/rhsm/rhsm.conf
processtimeout = 120
[root@ibm-x3650m4-01-vm-14 ~]# time /etc/cron.daily/rhsmd
real 2m0.030s <========== PROCESS TIMEDOUT AFTER 120 SECONDS, AS EXPECTED
user 0m0.576s
sys 0m0.109s
VERIFIED! After applying the 8.2 zstream fix subscription-manager-1.26.17-1.el8_2, the "processtimeout" configuration in all lowercase was honored by /etc/cron.daily/rhsmd
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-2020:2466