RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 730428 - libvirt lost SIGHUP reloading behavior
Summary: libvirt lost SIGHUP reloading behavior
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Osier Yang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-12 21:24 UTC by Eric Blake
Modified: 2011-12-06 11:26 UTC (History)
7 users (show)

Fixed In Version: libvirt-0.9.4-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 11:26:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1513 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2011-12-06 01:23:30 UTC

Description Eric Blake 2011-08-12 21:24:38 UTC 
Description of problem:
In the rebase to newer virNetServer, the libvirtd daemon accidentally lost its ability to react to SIGHUP as a clue to reload state.

Version-Release number of selected component (if applicable):
libvirt-0.9.4-2.el6

How reproducible:
100%

Steps to Reproduce:
1. killall -SIGHUP libvirtd
2.
3.
  
Actual results:
no state reload

Expected results:
state reload should happen

Additional info:
See upstream bug report:
https://www.redhat.com/archives/libvir-list/2011-August/msg00518.html
regression introduced by upstream commit df0b57a95a.
Comment 1 Daniel Veillard 2011-08-15 07:25:55 UTC 
Patch sent upstream:

https://www.redhat.com/archives/libvir-list/2011-August/msg00561.html

Daniel
Comment 2 Daniel Veillard 2011-08-15 07:53:35 UTC 
Upstream commit 9e093f0b4cc5a5fc455a4893d73dc0f2c5355161

Daniel
Comment 5 dyuan 2011-08-16 09:55:15 UTC 
Test result for libvirt-0.9.4-2.el6
# service libvirtd restart
Stopping libvirtd daemon:                                  [  OK  ]
Starting libvirtd daemon:                                  [  OK  ]

# virsh list --all
 Id Name                 State
----------------------------------
  - rhel6                shut off

# kill -SIGHUP `pidof libvirtd`

# ps aux|grep libvirtd

# virsh list --all
error: Failed to reconnect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused

# service libvirtd status
libvirtd dead but pid file exists


==============
Tested with libvirt-0.9.4-4.el6.

# virsh list --all
 Id Name                 State
----------------------------------
  - dom                  shut off

# ls /var/run/libvirt/qemu/
dom.pid
# ls /etc/libvirt/qemu
dom.xml  networks

# cp dom-create.xml /etc/libvirt/qemu

# kill -SIGHUP `pidof libvirtd`

# virsh list --all
 Id Name                 State
----------------------------------
  - dom                  shut off
  - dom-create           shut off

# ls /etc/libvirt/qemu
dom-create.xml  dom.xml  networks

======
repeat the "kill -SIGHUP"

# virsh list --all
 Id Name                 State
----------------------------------
  - dom                  shut off
  - dom-create           shut off
  - dom-create           shut off

start the dom-create
# virsh start dom-create
Domain dom-create started

# virsh list --all
 Id Name                 State
----------------------------------
  2 dom-create           running
  - dom                  shut off
  - dom-create           running

# ls /var/run/libvirt/qemu/
dom-create.pid  dom-create.xml  dom.pid
# ls /etc/libvirt/qemu
dom-create.xml  dom.xml  networks

======
repeat the "kill -SIGHUP"

# virsh list --all
 Id Name                 State
----------------------------------
  2 dom-create           running
  - dom                  shut off
  - dom-create           running
  - dom-create           running

# ls /var/run/libvirt/qemu/
dom-create.pid  dom-create.xml  dom.pid
# ls /etc/libvirt/qemu
dom-create.xml  dom.xml  networks
Comment 6 Osier Yang 2011-08-16 10:09:00 UTC 
> ======
> repeat the "kill -SIGHUP"
> 
> # virsh list --all
>  Id Name                 State
> ----------------------------------
>   2 dom-create           running
>   - dom                  shut off
>   - dom-create           running
>   - dom-create           running
> 
> # ls /var/run/libvirt/qemu/
> dom-create.pid  dom-create.xml  dom.pid
> # ls /etc/libvirt/qemu
> dom-create.xml  dom.xml  networks

Please file a new bug for this, we have problem on virStateReload, regardless of whether the SIGHUP handling is supported or not.
Comment 7 dyuan 2011-08-16 10:15:07 UTC 
Verified this bug as SIGHUP can reload the status now.
File a new bug 730937 to track the issue in comment 5.
Comment 8 errata-xmlrpc 2011-12-06 11:26:27 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.