Description of problem:
Version on 4 of the oVirt engine will support two versions of the API:
version 3, which will be backwards compatible with older versions of the
engine, and version 4, which won't be compatible. The default used by the
server will be version 4, but clients can explicitly request a version
of the API using the "Version" header or the "/v3" URL prefix. The
header is the preferred mechanism because it is just ignored by older
versions of the server. This patch modifies the oVirt fence agent so
that the path and version of the API are configuratble, and so that
their default values work correctly with version 3 compatibility mode of
From upstream patch:
Version-Release number of selected component (if applicable):
In one particular case fencing doesn't work with 4.0.11-47.el7_3.2 in RHEV 3.6:
Upgrading the fence-agents to 4.0.11-47.el7_3.2 breaks fencing, and downgrading it back to 4.0.11-27.el7_2.7 fixes it.
fence-agents-rhevm-4.0.11-27.el7_2.7 -- working
fence-agents-rhevm-4.0.11-47.el7_3.2 -- not working
We did a diff of the two versions  and we found out that in the new version we have a hard-coded api path (i.e. /api/) which is not backwards-compatible with RHEV 3.x:
< if opt.has_key("--api-path"):
< api_path = opt["--api-path"]
< api_path = "/ovirt-engine/api"
< url += "//" + opt["--ip"] + ":" + str(opt["--ipport"]) + api_path + "/" + command
> url += "//" + opt["--ip"] + ":" + str(opt["--ipport"]) + "/api/" + command
The problem seems to be resolved upstream already:
Can we get (rebase/cherry pick) the patch to the RH fence driver as well?
*** Bug 1402860 has been marked as a duplicate of this bug. ***
*** Bug 1423881 has been marked as a duplicate of this bug. ***
*** Bug 1468556 has been marked as a duplicate of this bug. ***
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.