Bug 660706
Summary: | do not start libvirt-guests on upgrade | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Dan Kenigsberg <danken> |
Component: | libvirt | Assignee: | Eric Blake <eblake> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.0 | CC: | abaron, bsarathy, cpelland, dallan, dyuan, eblake, gren, hateya, jdenemar, plyons, xen-maint, yoyzhang |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.8.7-2.el6 | Doc Type: | Bug Fix |
Doc Text: |
The %post script (part of the libvirt-client package) started the libvirt-guests service even when the service was explicitly turned off. With this update, the libvirt-guests service is no longer started when explicitly turned off.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-05-19 13:24:51 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: | |||
Bug Depends On: | |||
Bug Blocks: | 668694 |
Description
Dan Kenigsberg
2010-12-07 16:19:35 UTC
upstream patch in commit 91b3e1038f; will be picked up as part of rebasing libvirt for RHEL 6.1. Fixed upstream by v0.8.6-80-g91b3e10: commit 91b3e1038f32524304063c17e4dd56b9fb66f362 Author: Dan Kenigsberg <danken> Date: Tue Dec 7 18:05:44 2010 +0200 spec: do not start libvirt-guests if that service is off Built into libvirt-0.8.7-1.el6 Oops, libvirt.spec was not properly updated to upstream version and thus it doesn't contain this fix. I'll fix that in -2. # service libvirt-guests status started # service libvirt-guests stop Running guests on default URI: no running guests. # chkconfig --list libvirt-guests libvirt-guests 0:off 1:off 2:off 3:off 4:off 5:off 6:off # rpm -ivh libvirt-client-0.8.7-1.el6.x86_64.rpm --force Preparing... ########################################### [100%] 1:libvirt-client ########################################### [100%] # service libvirt-guests status started Tested fail with libvirt-client-0.8.7-2.el6.x86_64 - 2.6.32-94.el6.x86_64 - qemu-kvm-0.12.1.2-2.129.el6.x86_64 - libvirt-0.8.7-2.el6.x86_64 The test step and actual result is the same wtih comment 8 Are you sure libvirt-guests init script was turned off before upgrading to libvirt-0.8.7-2.el6.x86_64? You need to see the exact same output of chkconfig --list libvirt-guests as shown in comment 8. If you have the script on for any of the runlevels, the init script will be started (although it should probably be started only if it is on in current runlevel but that's a different issue). It works as expected for me. Thanks Jiri, my testing in comment 10 didn't make all run level off, and after #chkconfig libvirt-guests off, then test pass 1. # service libvirt-guests status started 2. # service libvirt-guests stop Running guests on default URI: no running guests. 3. # chkconfig libvirt-guests off # chkconfig --list libvirt-guests libvirt-guests 0:off 1:off 2:off 3:off 4:off 5:off 6:off 4. # rpm -Uvh libvirt-0.8.7-2.el6.x86_64.rpm libvirt-client-0.8.7-2.el6.x86_64.rpm libvirt-python-0.8.7-2.el6.x86_64.rpm Preparing... ########################################### [100%] 1:libvirt-client ########################################### [ 33%] 2:libvirt ########################################### [ 67%] 3:libvirt-python ########################################### [100%] 5. # service libvirt-guests status stopped, with saved guests Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The %post script (part of the libvirt-client package) started the libvirt-guests service even when the service was explicitly turned off. With this update, the libvirt-guests service is no longer started when explicitly turned off. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0596.html |