<div class="gmail_quote">On Thu, Apr 12, 2012 at 12:41 PM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com">iheim@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 04/12/2012 01:01 PM, Martin Hovmöller wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It looks to me like the options are dropped, especially since the<br>
fenceNode line from the hypervisor says "options=". What's going on here?<br>
When I try to save the power management configuration, the Options-field<br>
is empty the next time I go to Edit Host.<br>
Running fence_ipmilan manually works fine, both from the hypervisors and<br>
the manager.<br>
</blockquote>
<br></div>
sounds like a bug in the UI.<br>
please check from api to rule out an engine bug.<br>
btw, from this bug, it looks like it was only added to intended 3.1 release of ovirt in the ui?<br>
Bug 782703 - [webadmin] No power management options in GUI<br>
which was fixed mid-march<br>
<br>
this also seem in same area (could be fixed by now, but you are not using latest devel branch), so again, i'd check from api first:<br>
Bug 784790 - [ovirt][engine][webadmin] - power management - slot information is not being saved (bladecenter)<br>
<br>
</blockquote></div><br><div><div style>It does indeed seem to be an engine bug.</div><div style>The cli gives me the following info:</div><div style><div>oVirt shell (connected)]# show host rhevh1.domain</div><div><br></div>
<div>id : 4e6ccb2c-84c7-11e1-aecc-2c768aac9498</div><div>name : rhevh1.domain</div><div>address : 10.23.30.110</div><div>cluster-id : 99408929-82cf-4dc7-a532-9d998063fa95</div>
<div>cpu-name : AMD Opteron(tm) Processor 6174</div><div>cpu-speed : 2200.0</div><div>cpu-topology-cores : 6</div><div>cpu-topology-sockets : 1</div>
<div>iscsi-initiator : iqn.1994-05.com.redhat:a85815241216</div><div>ksm-enabled : True</div><div>memory : 25194135552</div><div>port : 54321</div>
<div>power_management-address : 10.0.102.150</div><div>power_management-enabled : True</div><div>power_management-options-option-name : power_wait</div><div>power_management-options-option-value: 4</div>
<div>power_management-options-option-name : lanplus</div><div>power_management-options-option-value: yes</div><div>power_management-type : ipmilan</div><div>power_management-username : root</div>
<div>status-state : up</div><div>storage_manager-priority : 5</div><div>storage_manager-valueOf : false</div><div>summary-active : 0</div><div>summary-migrating : 0</div>
<div>summary-total : 0</div><div>transparent_hugepages-enabled : True</div><div>type : rhel</div></div><div style><br></div><div style>So apparently the options are saved. They are lost if I edit the host and don't manually add the options again before clicking Ok, so it seems to be saving the options correctly, but not re-reading them. Manual fencing by klicking Power Management -> Restart fails as well, even though the options seem to be passwd correctly when I do that. The fact that this option exists means that the first bug you pointed out doesn't match, but the second one seems to be the same one I'm seeing.</div>
<div style><br><div>2012-04-12 20:48:19,307 INFO [org.ovirt.engine.core.bll.FencingExecutor] (http--0.0.0.0-8443-6) Executing <Status> Power Management command, Proxy Host:rhevh2.domain, Agent:ipmilan, Target Host:rhevh1.domain, Management IP:10.0.102.150, User:root, Options:power_wait=4,lanplus=yes</div>
<div>2012-04-12 20:48:19,309 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (http--0.0.0.0-8443-6) START, FenceVdsVDSCommand(vdsId = 6fdbf336-84c8-11e1-82ef-2c768aac9498, targetVdsId = 4e6ccb2c-84c7-11e1-aecc-2c768aac9498, action = Status, ip = 10.0.102.150, port = , type = ipmilan, user = root, password = ******, options = 'power_wait=4,lanplus=yes'), log id: 11a7cfb9</div>
<div>2012-04-12 20:48:21,529 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (http--0.0.0.0-8443-6) FINISH, FenceVdsVDSCommand, return: Test Failed, Host Status is: unknown. The fence-agent script reported the following error: Getting status of IPMI:10.0.102.150...Chassis power = Unknown</div>
<div>Failed</div><div>, log id: 11a7cfb9</div><div>2012-04-12 20:48:21,529 ERROR [org.ovirt.engine.core.bll.RestartVdsCommand] (http--0.0.0.0-8443-6) Failed to run RestartVdsCommand on vds :rhevh1.domain</div><div>2012-04-12 20:48:21,530 WARN [org.ovirt.engine.core.bll.RestartVdsCommand] (http--0.0.0.0-8443-6) CanDoAction of action RestartVds failed. Reasons:VDS_FAILED_FENCE_VIA_PROXY_CONNECTION,VDS_FENCING_OPERATION_FAILED,VAR__TYPE__HOST,VAR__ACTION__RESTART</div>
</div><div style><br></div><div style><br></div><div style>I'm trying to figure out how to try to fence a machine from the cli, but I can't figure out the correct syntax. The help seems to be a bit broken:<br><div>
[oVirt shell (connected)]# action host rhevh1.domain fence</div><div>error: </div><div>status: 400</div><div>reason: Bad Request</div><div>detail: Action [fenceType] required for fence<br><br></div></div><div style>Why do I need to specify fenceType when it's already stored for the host (and how do I specify it for that matter)?</div>
</div>