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.

Description of problem:

When testing the evacuation of compute nodes inside an OSPd8 environment we find out that certain instances (apparently randomly) fails to get provisioned again to a new compute node.

How reproducible:

Configure instance Ha in an OSPd environment like is described here: https://access.redhat.com/articles/1544823 and try to stop (echo c > /proc/sysrq-trigger) a compute node that is running instances.

Actual results:

The environment gets messed since the status of the instances is not clear.

Expected results:

Instances are provisioned to an alternative compute node.

Additional info:

It turned out that the problem is the way instances are selected (see here: https://github.com/ClusterLabs/fence-agents/blob/master/fence/agents/compute/fence_compute.py#L99) within the list function:

nova.servers.list(search_opts={'hypervisor': host})

this results in all the instances selected, so the filter criteria must be:

nova.servers.list(search_opts={'host': host})

tested with fence-agents-compute-4.0.11-33.el7.x86_64

[root@overcloud-compute-0 ~]# grep nova.servers.list /usr/sbin/fence_compute
	servers = nova.servers.list(search_opts={'host': options["--plug"]})

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-2016-2373.html