| Summary: | `service libvirt-guests status` may return 0 even if stopped | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Pelland <cpelland> |
| Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4 | CC: | abaron, acathrow, ajia, anton, bazulay, bili, danken, hklein, iheim, jdenemar, jiahu, jsvarova, jtomko, mgoldboi, nsoffer, pm-eus, tlavigne, xuzhang, ybronhei, yeylon |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.10.2-18.el6_4.15 | Doc Type: | Bug Fix |
| Doc Text: |
Whereas the status command of libvirt-guests init script returned "0" value when libvirt-guests service was stopped, LSB (Linux Standard Base) required a different value ("3") in such case. Consequently, other scripts relying on the return value could not distinguish whether the service was running or not. The libvirt-guests script has been fixed to conform with LSB and the "service libvirt-guests status" command now returns the correct value in the described scenario.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-13 10:29:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1011981 | ||
| Bug Blocks: | |||
|
Description
Chris Pelland
2013-10-09 12:25:10 UTC
Test with the latest libvirt 6.4.z build libvirt-0.10.2-18.el6_4.15.x86_64, the return value is always 3 now, so this bug is verified. Steps: 1. prepare one running guest. # virsh start a Domain a started 2. start the libvirt-guests service # service libvirt-guests start [root@xuzhangtest1 ~]# service libvirt-guests status started 3. stop the libvirt-guests service # service libvirt-guests stop Running guests on default URI: a Suspending guests on default URI... Suspending a: ... Suspending a: done 4. check the libvirt-guests service status # service libvirt-guests status stopped, with saved guests [root@xuzhangtest1 ~]# echo $? 3 5. start the libvirt-guests service again. ]# service libvirt-guests start Resuming guests on default URI... Resuming guest a: done [root@xuzhangtest1 ~]# service libvirt-guests status started 6. destroy the guest. # virsh list --all Id Name State ---------------------------------------------------- - a shut off 7. stop the libvirt-guests service # service libvirt-guests stop Running guests on default URI: no running guests. 8. check the libvirt-guests status [root@xuzhangtest1 ~]# service libvirt-guests status stopped, with no saved guests [root@xuzhangtest1 ~]# echo $? 3 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-1517.html |