Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
If for any reason it's required to cleanup a fence_compute agent, the whole set of cluster resources will be restarted and when fence_compute tries to connect to openstack nova it'll fail as it's not yet running. This will leave fence_compute resource in failed state, apparently in an endless loop.
Version-Release number of selected component (if applicable):
fence-agents-compute-4.0.11-47.el7_3.2.x86_64.rpm
How reproducible:
Seems to be reproducible only after fence_compute resource failing for the first time and when it requires a cleanup.
Steps to Reproduce:
1. pcs resource <fence_compute_resource_name> cleanup
Actual results:
fence_compute resource won't be able to start as openstack nova isn't yet running.
Sample logs:
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Nova connection failed. ClientException: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Nova connection failed. ClientException: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Nova connection failed. ClientException: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Couldn't obtain a supported connection to nova, tried: ['2.11', '2']
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Nova connection failed. ClientException: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Couldn't obtain a supported connection to nova, tried: ['2.11', '2']
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Please use '-h' for usage
Mar 03 08:39:14 overcloud-compute-0.localdomain fence_compute[24814]: Please use '-h' for usage
Expected results:
fence_compute should be able to start.
Additional info:
1. Solution is available at https://bugzilla.redhat.com/show_bug.cgi?id=1387590#c18
2. https://bugzilla.redhat.com/show_bug.cgi?id=1393789 says it's a clone of the above, but it's ERRATA doesn't include this specific fix.