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/ )
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>
Software Version:4.5.1.2-0.11.el8ev ipmilan agent has now dedicated Port field for setup
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.