Hide Forgot
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
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.
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/
Can you please test if this an issue with the latest virt-who builds?
It can't reproduce on latest virt-who-0.21.1-1.el7.noarch, therefore, verify it.
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.