The goal is to refactor current fencing flow to make it more transparent and configurable. The main goals will be:
1) Define unqiue interface to all fencing flow steps (SSH Soft Fencing, Kdump detection, hard fencing, ...)
2) Make each step easily configurable
3) Refactoring fencing flow code to make more understandable
More info will be posted later to feature page.
*** Bug 1128493 has been marked as a duplicate of this bug. ***
Created attachment 1014630 [details]
Last UX plan for the Power Management
Created attachment 1014643 [details]
Last sketches for Power Management
Created attachment 1014644 [details]
UX changes - Host Availability tab
we will add only Host Availability tab in this bug. The changes in Power Management tab are covered in BZ1198628.
So I replaced your attachment with correct one proposal.
When I stop network service on my host, engine is unable to automatically fence the host. Although it can restart the host if I restart it through power management manually.
Please do not fail RFE, please open separate bug and block this one for the tracking.
Documentation changes are already covered by BZ1255229
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.