Red Hat Bugzilla – Bug 1258864
fencing_policies is not available in REST API output
Last modified: 2016-02-10 14:14:33 EST
Description of problem:
There is not fencing policies section under cluster in REST API
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enable and change fencing_policy of cluster
2. curl -v -k -H 'Content-Type: application/xml' -u 'admin@internal:XXXXXX' -X GET https://rhevm.example.com//api/clusters/c81b57c6-350b-4a49-875b-a03732fc0874
No fencing_policies listed
Should be listed according to http://lists.ovirt.org/pipermail/engine-commits/2014-October/018489.html
Pavel, this feature will be included in 3.6 (see bug 1127592). There are no plans to include it in 3.5 at the moment. Do we need it in 3.5?
Eli, is is feasible to backport this to 3.5?
(In reply to Juan Hernández from comment #1)
> Pavel, this feature will be included in 3.6 (see bug 1127592). There are no
> plans to include it in 3.5 at the moment. Do we need it in 3.5?
> Eli, is is feasible to backport this to 3.5?
Yes it is, needs Oved ack on that
Oved, your input please.
Backporting this change doesn't seem complicated. It requires two patches, one to do a small change in the test infrastructure and another for the real feature:
restapi: Make mapper test more generic
core: adding API for Cluster Fencing Policy
Okay. Targeting to 3.5.5.
Pavel and Moran - please ack.
Please remember to ack and set the 3.5.z flag on the bugs required to regenerate the SDK as well, bug 1259211 and bug 1259214.
Thanks for the fast backporting!
The documentation should be updated too, accordingly for 3.5.5 and 3.6
setting missing ovirt-3.5.5 milestone for 3.5.5 bugs.
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.