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:
Looking at the source code (https://github.com/ClusterLabs/fence-agents/blob/master/fence/agents/rhevm/fence_rhevm.py ) , it appears it goes to /api and not /engine/api endpoint, so it'll fail against RHV 4.0.x and above.

*** This bug has been marked as a duplicate of bug 1402862 ***

(In reply to Marek Grac from comment #3)
> 
> *** This bug has been marked as a duplicate of bug 1402862 ***

Marek - this bug is a half of a line fix (just change the URL to /engine/api instead of /api )

The other bug require a bit more work.

@Yaniv:

Will /engine/api works will all older versions?

To be accurate, it is /ovirt-engine/api

As far as I remember it works in 3.6 and above (maybe also 3.5).
Juan - can you give a more accurate answer about it?

The recommended URL is /ovirt-engine/api since oVirt/RHV 3.5. Support for just /api was removed in oVirt/RHV 4.0.

Note also that the version of the fence agent included currently in RHEL already includes this patch (which hasn't been merged upstream):

  Explicitly use version 3 of the oVirt API
  https://github.com/ClusterLabs/fence-agents/pull/71

See bug 1287059 for details.

That means that it will already use /ovirt-engine/api by default, unless explicitly given the '--api-path' option with a different value.

Re-opening it, based on comment 7 - /ovirt-engine/api will work with v3.5 and above, so I suggest making this easy fix now, rather than the small rewrite that is needed to happen to v4 API.

This is fixed in bz#1422499.

*** This bug has been marked as a duplicate of bug 1422499 ***