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 1384181 - fence_virtd stops working if libvirtd is restarted
Summary: fence_virtd stops working if libvirtd is restarted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: fence-virt
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 18:23 UTC by Martin Stefany
Modified: 2019-03-06 00:40 UTC (History)
3 users (show)

Fixed In Version: fence-virt-0.3.2-13.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 09:47:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0680 0 None None None 2018-04-10 09:47:25 UTC

Description Martin Stefany 2016-10-12 18:23:11 UTC 
Description of problem:
If fence_virtd.service is used for fencing, and libvirtd.service gets restarted (due to what-ever reason), fence_virtd.service stops providing valid data.


Version-Release number of selected component (if applicable):
fence-virt-0.3.2-2.el7.x86_64
fence-virtd-0.3.2-2.el7.x86_64
fence-virtd-libvirt-0.3.2-2.el7.x86_64
fence-virtd-multicast-0.3.2-2.el7.x86_64
libvirt-1.2.17-13.el7_2.5.x86_64
libvirt-client-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-config-network-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-interface-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-lxc-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-qemu-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-secret-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-driver-storage-1.2.17-13.el7_2.5.x86_64
libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64
libvirt-python-1.2.17-2.el7.x86_64

How reproducible:
Always.


Steps to Reproduce:
1. Start libvirtd.service
2. Configure (e.g. http://clusterlabs.org/wiki/Guest_Fencing) and start fence_virtd.service
3. Test that `fence_xvm -o list` provides valid list of VMs
4. Restart libvirtd.service
5. Test that `fence_xvm -o list` now provides empty list

Actual results:
$ fence_xvm -o list
provides no output, thus no list of VMs


Expected results:
$ fence_xvm -o list
should provide list of VMs as before libvirtd.service restart


Additional info:
Quick workaround (and possible fix) is:
$ sudo systemctl edit fence_virtd.service
[Unit]
PartOf=libvirtd.service


Resulting in:
$ systemctl cat fence_virtd.service 
# /usr/lib/systemd/system/fence_virtd.service
[Unit]
Description=Fence-Virt system host daemon

After=basic.target
After=network.target
After=syslog.target
After=libvirt-qmf.service
After=libvirtd.service
After=corosync.service

Requires=basic.target
Requires=network.target

[Install]
WantedBy=multi-user.target

[Service]
Type=forking
Restart=on-failure
SysVStartPriority=99
Environment="FENCE_VIRTD_ARGS=-w"

# Autogenerated below here
EnvironmentFile=-/etc/sysconfig/fence_virtd
ExecStart=/usr/sbin/fence_virtd $FENCE_VIRTD_ARGS

# /etc/systemd/system/fence_virtd.service.d/override.conf
[Unit]
PartOf=libvirtd.service

And invoking fence_virtd.service restart once libvirtd.service is restarted.
Comment 2 Ryan McCabe 2017-07-24 19:36:08 UTC 
This is a result of a bug in the fence-virtd plugins that has since been fixed upstream. I think the better route is to apply that patch instead of relying on systemd to automatically restart.
Comment 8 errata-xmlrpc 2018-04-10 09:47:01 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.

https://access.redhat.com/errata/RHBA-2018:0680
Note You need to log in before you can comment on or make changes to this bug.