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.

In the RHEL 7.0 version of fence_ipmilan (written in C), sending options on STDIN handled the "lanplus" boolean without assigning a value (a line that just said "lanplus" enabled the lanplus option).  The RHEL 7.1 version was rewritten in python, and now "lanplus=1" is required (a simple "lanplus" line appears to be ignored).

This is a behavior regression.  I ran into it running oVirt and setting just "lanplus" as an IPMI fencing option, rather than "lanplus=1".

@Chris:

We know about this issue (last few days) but we are still trying to resolve it properly. Problem is not a fix itself (trivial) but this was not documented feature and fact that it work was more bug than a feature.

(In reply to Chris Adams from comment #0)
> This is a behavior regression.  I ran into it running oVirt and setting just
> "lanplus" as an IPMI fencing option, rather than "lanplus=1".

Thank you Chris for finding this workaround I was needing when meeting this same issue.

Accepting 'lanplus' is considered as a bug. Correct is 'lanplus=1' as can be entered in XML configuration of cluster.conf