Description of problem:
Fence devices like iLO3 and iDrac utilize fence_ipmilan, but there is confusion among users because they see things like:
fence_ilo and fence_drac5 and try to use those agents instead of using IPMI
So for certain cases like iLO3 and iDrac it may be worthwhile to create a symlink to fence_ipmilan so that it is more obvious that those devices map to the IPMI based fence agent.
So what I can see would be:
In addition, we might be able to optimize user experience by detecting which file was called and then setting args based on that. For example, if fence_ilo3 was called, then fence_ipmilan can automatically set power_wait to be 4 (if it was not explicitly set)
Created attachment 591829 [details]
This patch adds support for creating symlink fence agents for fencing library (example with ilo2) and ipmilan (example with ilo3). We will have to decide which symlinks should be added.
Patches are in upstream:
Unit test for (fence_ilo2, fence_ilo3, fence_imm, fence_idrac)
fence_? -o metadata
Functionality of agents needs to be checked only for fence_ilo3 (different default values)
fence_ilo3 -o status -l LOGIN -p PASS -a IP
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.