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 1111384 - fence-virt can't fence dead VMs
Summary: fence-virt can't fence dead VMs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: fence-virt
Version: 7.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On: 1104740
Blocks: 1111381 1113520
TreeView+ depends on / blocked
 
Reported: 2014-06-19 22:27 UTC by Ryan McCabe
Modified: 2019-03-06 02:16 UTC (History)
6 users (show)

Fixed In Version: fence-virt-0.3.2-1.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of: 1104740
Environment:
Last Closed: 2015-03-05 10:21:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0432 0 normal SHIPPED_LIVE fence-virt bug fix update 2015-03-05 14:52:10 UTC

Description Ryan McCabe 2014-06-19 22:27:52 UTC 
+++ This bug was initially created as a clone of Bug #1104740 +++

There is an issue in fence-virt virt backend in the way the list of Domains are gathered from the libvirt.

One simple test:

start a bunch of VMs...

[root@rhel6-ha-node1 ~]# fence_xvm -o list
Could not read /etc/cluster/fence_xvm.key; trying without authentication
rhel6-ha-node1       c632d8b3-875e-490a-85b0-94e233d04b68 on
rhel6-ha-node2       ba1274ec-1d43-4b39-a71f-e85b90fc7586 on
rhel6-ha-node3       c444b48e-6b50-466e-a685-fddd49ed171c on
rhel6-ha-node4       c5cbee4d-06ac-44bb-adf5-78aaf5a2a541 on

from the host find the qemu process for one of the VM. kill -9...

[root@rhel6-ha-node1 ~]# fence_xvm -o list
Could not read /etc/cluster/fence_xvm.key; trying without authentication
rhel6-ha-node1       c632d8b3-875e-490a-85b0-94e233d04b68 on
rhel6-ha-node2       ba1274ec-1d43-4b39-a71f-e85b90fc7586 on
rhel6-ha-node3       c444b48e-6b50-466e-a685-fddd49ed171c on

At this point the cluster is stuck because fence_virtd is unable to find the domain running and won't take any action.

The issue in the code is located in server/virt*.c:

virt_list_t *vl_get(virConnectPtr vp, int my_id)

we use virConnectNumOfDomains that only list active VMs and it's also racy with ListDomain.

We should change all that code to virConnectListAllDomains that can list both active and dead (including filters) to find the VM we need to fence and it's not racy.
Comment 4 errata-xmlrpc 2015-03-05 10:21:35 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://rhn.redhat.com/errata/RHBA-2015-0432.html
Note You need to log in before you can comment on or make changes to this bug.