Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:

fence_ilo2->fence_ilo
fence_ilo3->fence_ipmilan
fence_idrac->fence_ipmilan
fence_imm->fence_ipmilan

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]
Proposed patch

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:

http://git.fedorahosted.org/git/?p=fence-agents.git;a=commit;h=87266bcbf3f1b71664e65d82fb6de9f8814cb19e

http://git.fedorahosted.org/git/?p=fence-agents.git;a=commit;h=cd73f094f7c163aca57a1dc9d5138fb468846835

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.

http://rhn.redhat.com/errata/RHBA-2013-0286.html