Created attachment 1067725 [details]
Description of problem:
When I stop network service on host machine, is stops responding in engine and the host should be automatically fenced, but the stop command never succeeds.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. log into hosts console
2. stop network service
3. wait for host to be fenced
Host can be fenced manually.
Created attachment 1069314 [details]
the log is cut to relevant parts
Also the second host is not used at all for stop operation
Created attachment 1069724 [details]
engine log + debug
I found the issue: newest vdsm reports as supported cluster levels only 3.4+ but on engine we support cluster levels 3.0+. This change covered in BZ1229177 was merged later than fencing refactoring patches (before this change vdsm also reported 3.0+), so that's why we haven't found out it sooner.
When we test if the host can be used as a fencing proxy we check if it supports fencing policy for the cluster using: "is minimal supported version for fencing policy contained in version set reported by VDSM" (as noted above minimal support version in engine is 3.0 vs. 3.4 in VDSM). So we will have to change this condition to: "is there a version in VDSM version set which is higher or equal to minimal version need for fencing policy".
Without this change engine is not capable to fence any host in cluster with version <= 3.4 and also hosts in 3.5+ cluster if options "skip fencing if connected to storage" and "skip fencing if connectivity issues" were disable in cluster fencing policy.
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.