Red Hat Bugzilla – Bug 1092848
virt-who dies when the system is being unregistered
Last modified: 2016-11-30 19:32:56 EST
Description of problem: system has been unregistered, However, virt-who still run normally Version-Release number of selected component (if applicable): virt-who-0.9-2.el5 subscription-manager-1.8.22-1.el5 python-rhsm-1.8.18-1.el5 How reproducible: Always Steps to Reproduce: 1. Register system to SAM server and make sure virt-who run normally 2. Unregister system to SAM server [root@dhcp-128-110 libvirt-test-API]# subscription-manager unregister [root@dhcp-128-110 libvirt-test-API]# subscription-manager identity This system is not yet registered. Try 'subscription-manager register --help' for more information. 3. Check the virt-who status [root@dhcp-128-110 libvirt-test-API]# service virt-who status virt-who (pid 32168) is running... Actual results: virt-who still run normally after system unregistered to SAM server Expected results: Unregister that system, and virt-who can no longer authenticate to report hosts. so virt-who should stop after system has been unregistered. Additional info: As bug 1009230 is not a bug, it should be a bug
Currently, virt-who service is still running even if the system is not registered. It just doesn't report the host/guest associations to SAM. Once the system is registered, virt-who will start working propertly. There are two possible behaviors of virt-who when system is not registered (or been unregistered): 1) Exit immediately and refuse to start until registration 2) Start anyway (or continue to run) when unregistered, start sending host-guest associations after registration I'm not sure which one would be better but I agree that the behavior should be consistent across RHEL versions. Any ideas which approach is better?
I've decided that we should go with 2). It's how virt-who behaves on all supported RHELs. When the system is unregistered, virt-who obtains SIGHUP signal to reload it's configuration. There is bug in handling this signal that causes death of virt-who. I'll use this bug to fix it. It's the same bug as 1009230 (for RHEL-6), so I'll reopen it.
Upstream commit that fixes this issue: https://git.fedorahosted.org/cgit/virt-who.git/commit/.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Fixed in virt-who-0.9-4.el5.
Verified it on virt-who-0.9-4.el5
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. http://rhn.redhat.com/errata/RHBA-2014-1206.html