Hide Forgot
Description of problem: no "shutdown" operation is called when the libvirt daemon is restarted at first time. Version-Release number of selected component (if applicable): libvirt-0.8.7-13.el6 How reproducible: always Steps to Reproduce: 1. create /etc/libvirt/hooks/daemon. # cat /etc/libvirt/hooks/daemon #! /bin/bash echo "$0" "$@" >> /tmp/daemon.log exit 1 2. # chmod +x /etc/libvirt/hooks/daemon 3. restart libvirtd # service libvirtd restart 4. check /tmp/daemon.log. Actual results: /etc/libvirt/hooks/daemon - start - start Expected results: /etc/libvirt/hooks/daemon - shutdown - shutdown /etc/libvirt/hooks/daemon - start - start Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
patch posted to upstream: commit 32398e128205c92ed72b04b25279c9a4e5cb5e02 Author: Osier Yang <jyang> Date: Thu Apr 28 14:48:26 2011 +0800 util: Initialize hooks at daemon shutdown if no hooks defined We support to initialize the hooks at daemon reload if there is no hooks script is defined, we should also support initialize the hooks at daemon shutdown if no hooks is defined. To address bz: https://bugzilla.redhat.com/show_bug.cgi?id=688859
This should be fixed by the libvirt-0.9.2-1.el6 rebase
libvirt-0.9.2-1.el6.x86_64 qemu-kvm-0.12.1.2-2.165.el6.x86_64 kernel-2.6.32-156.el6.x86_64 Test steps : 1. create /etc/libvirt/hooks/daemon. # cat /etc/libvirt/hooks/daemon #! /bin/bash echo "$0" "$@" >> /tmp/daemon.log exit 1 2. # chmod +x /etc/libvirt/hooks/daemon 3. restart libvirtd # service libvirtd restart 4. check /tmp/daemon.log. Actual results: /etc/libvirt/hooks/daemon - shutdown - shutdown /etc/libvirt/hooks/daemon - start - start So bug fixed .
Set it as VERIFIED per comment5
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-2011-1513.html