Bug 1828186
| Summary: | /etc/cron.daily/rhsmd fails to recognize rhsmd.processtimeout configuration [rhel-7.8.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | subscription-manager | Assignee: | candlepin-bugs |
| Status: | CLOSED ERRATA | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.9 | CC: | candlepin-bugs, jsefler, redakkan, rhsm-qe, wpoteat |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1827711 | Environment: | |
| Last Closed: | 2020-05-12 18:40:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1827711 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2020-04-27 09:17:16 UTC
Verifying Version... [root@intel-chiefriver-02 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.8 (Maipo) [root@intel-chiefriver-02 ~]# rpm -q subscription-manager subscription-manager-1.24.26-3.el7_8.x86_64 [root@intel-chiefriver-02 ~]# rpm -q --changelog subscription-manager | grep 1828186 - 1828186: Make rhsmd cron read 'processTimeout' case-insensitive [root@intel-chiefriver-02 ~]# To demonstrate that this bug is fixed (as originally reported in Bug 1827708 on a RHEL-8.2 machine), we will show that as a result of an upgrade to RHEL-7.8 (steps not shown) the /etc/rhsm/rhsm.conf file may be absent of a "processTimeout" configuration. Despite its absence, we can use subscription-manager config tool to change the value of the default "processtimeout" value (from 300 seconds) to a different value and it will be honored. [root@intel-chiefriver-02 ~]# grep --ignore-case "processTimeout" /etc/rhsm/rhsm.conf [root@intel-chiefriver-02 ~]# [root@intel-chiefriver-02 ~]# subscription-manager config | grep --ignore-case "processTimeout" processtimeout = [300] [root@intel-chiefriver-02 ~]# [root@intel-chiefriver-02 ~]# subscription-manager config --rhsmd.processtimeout=120 [root@intel-chiefriver-02 ~]# [root@intel-chiefriver-02 ~]# subscription-manager config | grep --ignore-case "processTimeout" processtimeout = 120 [root@intel-chiefriver-02 ~]# [root@intel-chiefriver-02 ~]# grep --ignore-case "processTimeout" /etc/rhsm/rhsm.conf processtimeout = 120 [root@intel-chiefriver-02 ~]# [root@intel-chiefriver-02 ~]# time /etc/cron.daily/rhsmd real 2m0.024s <==== VERIFIED: The process exited after a 120 second timeout as newly configured user 0m0.198s sys 0m0.058s [root@intel-chiefriver-02 ~]# VERIFIED: We invoked "subscription-manager config --rhsmd.processtimeout=120" on an upgraded RHEL7 system to change the default "processtimeout" which was honored by the /etc/cron.daily/rhsmd job. Note: The fix for this bug was a simple code change in /etc/cron.daily/rhsmd to introduce an "--ignore-case" option to the first line of code in /etc/cron.daily/rhsmd. Let's look at that line of code on this rhel7.8 system.... [root@intel-chiefriver-02 ~]# head -n5 /etc/cron.daily/rhsmd #!/bin/sh # nightly run of rhsmd to log entitlement expiration/validity errors to syslog # this is a cron job because it doesn't need to 'phone home'. should that # change, look into calling the dbus interface from rhsmcertd instead. config=$(grep -iE "^processTimeout" /etc/rhsm/rhsm.conf | grep -Po "[0-9]+") ^ ^ That is the one character fix for "--ignore-case". 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:2101 |