Hide Forgot
Description of problem: RHV is going to be deprecated v3 API in a year. v4 API is already available from 4.0 (Aug 2016) - the agent should move to the new API. Personally, I'd create fence-rhvm4 agent.
@Yaniv: Would it be possible to have API that will last (almost) forever? I have no issues with building fence_rhevm4 but it will be harder to add a new packages to RHEL7 in next years.
(In reply to Marek Grac from comment #2) > @Yaniv: > > Would it be possible to have API that will last (almost) forever? I have no > issues with building fence_rhevm4 but it will be harder to add a new > packages to RHEL7 in next years. For the lifecycle of RHV 4.x, the v4 API will be supported. That's several years.
*** Bug 1402860 has been marked as a duplicate of this bug. ***
(In reply to Yaniv Kaul from comment #3) Will it be backwards compatible with v3 as mentioned in the following bz? https://bugzilla.redhat.com/show_bug.cgi?id=1422499#c0
(In reply to Oyvind Albrigtsen from comment #5) > (In reply to Yaniv Kaul from comment #3) > Will it be backwards compatible with v3 as mentioned in the following bz? > https://bugzilla.redhat.com/show_bug.cgi?id=1422499#c0 No, v4 is completely different.
Bumping to 7.6.
https://github.com/ClusterLabs/fence-agents/pull/269
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://access.redhat.com/errata/RHSA-2019:2037