Bug 1222098

Summary: fence_ipmilan rewrite regression on option parsing
Product: Red Hat Enterprise Linux 7 Reporter: Chris Adams <linux>
Component: fence-agentsAssignee: Marek Grac <mgrac>
Status: CLOSED NOTABUG QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: cluster-maint, nicolas, qguo
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1235218 (view as bug list) Environment:
Last Closed: 2016-01-20 15:40:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Adams 2015-05-15 18:29:57 UTC 
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".
Comment 2 Marek Grac 2015-05-17 20:20:56 UTC 
@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.
Comment 3 Nicolas Ecarnot 2015-05-20 07:12:53 UTC 
(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.
Comment 5 Marek Grac 2016-01-20 15:40:54 UTC 
Accepting 'lanplus' is considered as a bug. Correct is 'lanplus=1' as can be entered in XML configuration of cluster.conf