Bug 2087886

Summary:	ipmilan fencing agent configuration panel misses port option and passing it as option ends up with losing the parameter
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	BLL.Infra	Assignee:	Eli Mesika <emesika>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavol Brilla <pbrilla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.5.0.8	CC:	bugs, dfodor, mperina
Target Milestone:	ovirt-4.5.1	Flags:	mperina: ovirt-4.5+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.1.1	Doc Type:	Release Note
Doc Text:	port option will be always visible for ipmilan fence agent, so admin can override the default port directy (and not using options field) if needed	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-23 05:54:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2022-05-18 14:14:33 UTC

When setting up power management, selecting ipmilan agent there's no `port` option.

While setting up the configuration you can set as an example "port=6230,lanplus=1" and the verification passes.

Once you save the configuration and exit, returning to the agent configuration only shows `lanplus=1` loosing the port parameter.


This ends up to be problematic if your power controller has same IP but different port for managing different hosts (like in virtualized environments with VirtualBMC https://docs.openstack.org/virtualbmc/latest/ )

Comment 2 Eli Mesika 2022-05-29 11:43:29 UTC

Investigation :

Reproduced om master , however the options are stored correctly in DB but not read correctly from UI 
using API brings the correct result when "options=lanplus=1,port=1111" :

<agents>
  <agent href="/ovirt-engine/api/hosts/dc7cefb5-b6a9-4962-9329-e8d35ef01a8f/fenceagents/4f5f0bc5-b89b-449c-898d-1206e5d4cdb2" id="4f5f0bc5-b89b-449c-898d-1206e5d4cdb2">
    <address>10.37.160.42</address>
    <encrypt_options>false</encrypt_options>
    <options>
      <option>
        <name> port</name>
        <value>1111</value>
      </option>
      <option>
        <name>lanplus</name>
        <value>1</value>
      </option>
    </options>
    <order>1</order>
    <port>1111</port>
    <type>ipmilan</type>
    <username>admin</username>
    <host href="/ovirt-engine/api/hosts/dc7cefb5-b6a9-4962-9329-e8d35ef01a8f" id="dc7cefb5-b6a9-4962-9329-e8d35ef01a8f"/>
  </agent>
</agents>

Comment 3 Pavol Brilla 2022-06-22 16:59:30 UTC

Software Version:4.5.1.2-0.11.el8ev
ipmilan agent has now dedicated Port field for setup

Comment 4 Sandro Bonazzola 2022-06-23 05:54:58 UTC

This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.