Description of problem:
Power management TEST button fails always in 3.4 DC/Cluster
Commit 52bee82409eee65ef22af805b21113afa1b76a03 adds Fencing Policy support.
One of the changes was in FenceExecutor:isAgentSupported
code added that cause the problem :
--start--
ret = ret && _vds.getSupportedClusterVersionsSet().contains(minVersionSupportingFencingPol);
--end--
The second value in the && operator is constantly false when doing a TEST from UI (this actually calls GetNewVdsFenceStatusQuery)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.Define 2 hosts in a 3.4 cluster
2.Add valid PM settings to one of teh Hosts
3.Click the TEST button
Actual results:
TEST fails with a message that no proxy host found in the Cluster/DC
Expected results:
TEST should succeed
Additional info:
The problem is, that VDS instance passed to FenceExecutor is not properly filled,
only PM options are present, but cluster level compatibility needed for fencing policy check is null. Since fencing policy is used only for VdsNonRespondingTreatment, best solution will be to check fencing policy only when it's present.