Bug 1775714
| Summary: | rhsmd process never exits | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Taft Sanders <tasander> |
| Component: | subscription-manager | Assignee: | Jiri Hnidek <jhnidek> |
| Status: | CLOSED ERRATA | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.7 | CC: | cdonnell, csnyder, jhnidek, redakkan, skallesh, wpoteat, yong.zhou |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-29 19:22:47 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
Taft Sanders
2019-11-22 16:14:55 UTC
rhsmd is not specifically for informing rhsm-icon, but also other items within the subscription-manager chain. That is to say that this informs multiple (or available) pieces about changes in entitlement status (including via DBus API) to trigger notifications or actions. That makes restating that this bug is that after running `subscription-manager status`, rhsmd is triggered and never ends (hangs). This could be environmental based on networking, or there could be an issue with rhsmd's execution in this scenario (likely). *** Bug 1775713 has been marked as a duplicate of this bug. *** The impact is actaully severe. When rhsmd doesn't exits, it continues to talk to satellite server and drive up load. In large enviroment we can see degradation of performance over time. I can reproduce the the bug report for several cases. 1. case When a system is not registered and I run status command, then I'm able to reproduce the bug report: [root@fedora30 candlepin]# ps aux | grep rhsmd root 22311 0.0 0.0 215744 900 pts/1 S+ 16:22 0:00 grep --color=auto rhsmd [root@fedora30 candlepin]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Unknown System Purpose Status: Unknown [root@fedora30 candlepin]# ps aux | grep rhsmd root 22314 11.0 2.6 306412 54512 ? Ss 16:22 0:00 /usr/bin/python3 /usr/libexec/rhsmd root 22316 0.0 0.0 215744 896 pts/1 S+ 16:22 0:00 grep --color=auto rhsmd Interesting is that clean command stops rhsmd process [root@fedora30 candlepin]# subscription-manager clean All local data removed [root@fedora30 candlepin]# ps aux | grep rhsmd root 22331 0.0 0.0 215744 892 pts/1 S+ 16:23 0:00 grep --color=auto rhsmd 2. case When system is compliant, then I can reproduce starting of rhsmd too: [root@fedora30 candlepin]# subscription-manager register --username admin --password admin --org admin Registering to: svice:8443/candlepin The system has been registered with ID: 66091455-7d18-4b0a-88e2-f2d8976b40b6 The registered system name is: fedora30 [root@fedora30 candlepin]# ps aux | grep rhsmd root 22442 0.0 0.0 215744 832 pts/1 S+ 16:24 0:00 grep --color=auto rhsmd [root@fedora30 candlepin]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Invalid SP Additional bits: - Not supported by a valid subscription. Fake OS Bits: - Not supported by a valid subscription. System Purpose Status: Mismatched - The requested add-on "" is not provided by a currently consumed subscription. [root@fedora30 candlepin]# ps aux | grep rhsmd root 22444 5.1 2.7 306412 54816 ? Ss 16:24 0:00 /usr/bin/python3 /usr/libexec/rhsmd root 22459 0.0 0.0 215744 896 pts/1 S+ 16:24 0:00 grep --color=auto rhsmd [root@fedora30 candlepin]# subscription-manager attach --auto Installed Product Current Status: Product Name: Fake OS Bits Status: Subscribed Product Name: SP Additional bits Status: Subscribed [root@fedora30 candlepin]# ps aux | grep rhsmd root 22556 0.0 0.0 215744 832 pts/1 S+ 16:25 0:00 grep --color=auto rhsmd It is interesting that attaching required pools using --auto option stops rhsmd too. 3. case When system is current and I run status command, then only unregistering can stops rhsmd process: [root@fedora30 candlepin]# ps aux | grep rhsmd root 22556 0.0 0.0 215744 832 pts/1 S+ 16:25 0:00 grep --color=auto rhsmd [root@fedora30 candlepin]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Current System Purpose Status: Mismatched - The requested add-on "" is not provided by a currently consumed subscription. [root@fedora30 candlepin]# ps aux | grep rhsmd root 22634 8.2 2.7 306412 54960 ? Ss 16:30 0:00 /usr/bin/python3 /usr/libexec/rhsmd root 22647 0.0 0.0 215744 896 pts/1 S+ 16:30 0:00 grep --color=auto rhsmd It is necessary to mention that rhsm-icon (part of subscription-manager-gui) cannot be running to be able to reproduce cases in step #13. rhsm-icon is automatically started using XDG (/etc/xdg/autostart/rhsm-icon.desktop), when user uses desktop environment (GNOME/KDE) and is logged-in. Moving bug to verified as I dont see rhsmd process running status or attach or register command [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager version server type: This system is currently not registered. subscription management server: 2.9.21-1 subscription management rules: 5.37 subscription-manager: 1.24.32 Case 1: [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager identity This system is not yet registered. Try 'subscription-manager register --help' for more information. [root@hpe-dl380pgen8-02-vm-4 ~]# ps aux | grep rhsmd root 26333 0.0 0.0 112808 936 pts/0 S+ 18:10 0:00 grep --color=auto rhsmd [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Unknown System Purpose Status: Unknown [root@hpe-dl380pgen8-02-vm-4 ~]# ps aux | grep rhsmd root 26348 0.0 0.0 112808 936 pts/0 S+ 18:11 0:00 grep --color=auto rhsmd Case2: [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager register --serverurl subscription.rhsm.stage.redhat.com --username qa --password redhatqa --auto-attach --force Registering to: subscription.rhsm.stage.redhat.com:443/subscription The system has been registered with ID: 61a80d71-c29f-4cff-9e6c-1f3485627232 The registered system name is: hpe-dl380pgen8-02-vm-4.hpe2.lab.eng.bos.redhat.com Installed Product Current Status: Product Name: Red Hat Enterprise Linux 7 Server High Touch Beta Status: Subscribed Product Name: Red Hat Enterprise Linux Server Status: Subscribed [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Current System Purpose Status: Not Specified [root@hpe-dl380pgen8-02-vm-4 ~]# ps aux | grep rhsmd root 26463 0.0 0.0 112808 936 pts/0 S+ 18:12 0:00 grep --color=auto rhsmd Case 3: [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager remove --all 1 local certificate has been deleted. 1 subscription removed at the server. [root@hpe-dl380pgen8-02-vm-4 ~]# subscription-manager status +-------------------------------------------+ System Status Details +-------------------------------------------+ Overall Status: Invalid Red Hat Enterprise Linux Server: - Not supported by a valid subscription. Red Hat Enterprise Linux 7 Server High Touch Beta: - Not supported by a valid subscription. System Purpose Status: Not Specified [root@hpe-dl380pgen8-02-vm-4 ~]# ps aux | grep rhsmd root 26499 0.0 0.0 112808 936 pts/0 R+ 18:12 0:00 grep --color=auto rhsmd I'm adding another link to the PR that is related to this issue. 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 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-2020:3866 |