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.

Bug 1401760

Summary: virt-who processes(PPID = 1) cannot be killed immediately after stop virt-who service
Product: Red Hat Enterprise Linux 7 Reporter: Liushihui <shihliu>
Component: virt-whoAssignee: Chris Snyder <csnyder>
Status: CLOSED CURRENTRELEASE QA Contact: Eko <hsun>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: khowell, redakkan, yuefliu
Target Milestone: pre-dev-freezeKeywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-11 11:18:23 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 Liushihui 2016-12-06 02:32:19 UTC 
Description of problem:
When virt-who run at xen mode, stop virt-who service, virt-who processes(PPID != 1) cannot be killed immediately after stop virt-who service

Version-Release number of selected component (if applicable):
virt-who-0.18-1.el6.noarch
subscription-manager-1.18.5-1.el6.x86_64
python-rhsm-1.18.5-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Register system to stage candlepin

2. Config virt-who run at xen mode 
[root@hp-dl320egen8-01 ~]# cat /etc/sysconfig/virt-who  | grep -v ^# | grep -v ^$
VIRTWHO_DEBUG=1
VIRTWHO_XEN=1
VIRTWHO_XEN_OWNER=7970632
VIRTWHO_XEN_ENV=7970632
VIRTWHO_XEN_SERVER=10.73.131.133
VIRTWHO_XEN_USERNAME=root
VIRTWHO_XEN_PASSWORD=Welcome1

3. Restart virt-who service and check virt-who threads
[root@hp-dl320egen8-01 ~]# service virt-who restart
Stopping virt-who:                                         [FAILED]
Starting virt-who:                                         [  OK  ]
[root@hp-dl320egen8-01 ~]# ps -ef|grep virt-who
root     54923     1  0 21:13 ?        00:00:00 /usr/bin/python /usr/bin/virt-who
root     54927 54923  1 21:13 ?        00:00:00 /usr/bin/python /usr/bin/virt-who
root     54933 54708  0 21:14 pts/0    00:00:00 grep virt-who

4. Stop virt-who service and check virt-who threads
[root@hp-dl320egen8-01 ~]# service virt-who stop
Stopping virt-who:                                         [  OK  ]
[root@hp-dl320egen8-01 ~]# ps -ef|grep virt-who
root     54927     1  1 21:13 ?        00:00:00 /usr/bin/python /usr/bin/virt-who
root     54964 54708  0 21:14 pts/0    00:00:00 grep virt-who
[root@hp-dl320egen8-01 ~]# ps -ef|grep virt-who
root     54927     1  1 21:13 ?        00:00:00 /usr/bin/python /usr/bin/virt-who
root     54966 54708  0 21:14 pts/0    00:00:00 grep virt-who

Actual results:
Although virt-who has been stop successfully, Virt-who thread(PPID = 1) can't be killed until 5s.

Expected results:
Virt-who thread(PPID = 1) should be killed immediately after stop virt-who service. 

Additional info:
When virt-who run at esx mode, it hasn't this problem
Comment 2 yuefliu 2017-02-08 04:50:50 UTC 
The same issue reproduce when shutdown xenserver to make virt-who run in abnormal.

Steps to Reproduce:
1. register RHEL-6.9-20170202.0 host to satellite5.7 with xen mode.

2. start virt-who service and check virt-who threads.
# service virt-who restart
# ps -ef |grep virt-who
root    2795     1  1 22:34 ?       00:00:00 /usr/bin/python /usr/bin/virt-who
root    2799  2795  5 22:34 ?       00:00:00 /usr/bin/python /usr/bin/virt-who
root    2808  2246  0 22:34 pts/1   00:00:00 grep virt-who

3. shutdown xenserver host.

4. restart virt-who service and check virt-who threads again.
# service virt-who restart
# ps -ef |grep virt-who
root    2799     1  0 22:34 ?       00:00:00 /usr/bin/python /usr/bin/virt-who
root    2849     1  0 22:35 ?       00:00:00 /usr/bin/python /usr/bin/virt-who
root    2853  2849  0 22:35 ?       00:00:15 /usr/bin/python /usr/bin/virt-who
root    3019  2246  0 23:30 pts/1   00:00:00 grep virt-wh

Actual results:
two virt-who threads(PPID = 1) exist and cannot be killed even start the xenserver host.
Comment 5 Jan Kurik 2017-12-06 10:28:01 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Comment 7 Kevin Howell 2017-12-14 15:04:19 UTC 
Can you please test if this an issue with the latest virt-who builds?
Comment 8 Liushihui 2017-12-15 02:35:47 UTC 
It can't reproduce on latest virt-who-0.21.1-1.el7.noarch, therefore, verify it.
Comment 9 Rehana 2020-12-11 11:18:23 UTC 
Old bug clean up :
================

Closing the bug with Current release ,the bug was verified by QE during a RHEL release cycle but was not closed.