Bug 806226
Summary: | virt-who dead but pid file exists | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Hui Wang <huiwang> |
Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
Status: | CLOSED ERRATA | QA Contact: | Entitlement Bugs <entitlement-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.9 | CC: | khong, ovasik, wili |
Target Milestone: | alpha | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-who-0.7-1.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-08 07:35:34 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: |
Description
Hui Wang
2012-03-23 09:14:28 UTC
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. This bug has been fixed in virt-who-0.7-1.el5. Moving to verified. version: virt-who-0.7-4.el5 subscription-manager-firstboot-1.0.13-1.el5 subscription-manager-1.0.13-1.el5 subscription-manager-gui-1.0.13-1.el5 python-rhsm-1.0.5-1.el5 katello-headpin-all-0.2.13-1.el6_2.noarch candlepin-0.6.5-1.el6_2.noarch Step: 1. Run "ssh root@$remote_machine1_ip "service virt-who restart"" on machine2 # ssh 10.66.13.64 "service virt-who restart" root.13.64's password: Stopping virt-who: [ OK ] Starting virt-who: [ OK ] [root@localhost wanghui]# 2. Check the virt-who service status on machine1 # service virt-who status virt-who (pid 434) is running... 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-2013-0072.html |