12:58 p.m.
----- Original Message -----
From: "Dmitriy A Pyryakov"
<DPyryakov(a)ekb.beeline.ru>
To: "Eli Mesika" <emesika(a)redhat.com>
Cc: "Itamar Heim" <iheim(a)redhat.com>, users(a)ovirt.org
Sent: Thursday, September 20, 2012 12:05:58 PM
Subject: Re: [Users] HP Integrated Lights Out 3
Eli Mesika <emesika(a)redhat.com> написано 20.09.2012 14:55:41: > От:
Eli Mesika <emesika(a)redhat.com> > Кому: Dmitriy A Pyryakov
<DPyryakov(a)ekb.beeline.ru>
> Копия: users(a)ovirt.org, Itamar Heim <iheim(a)redhat.com>
> Дата: 20.09.2012 14:55
> Тема: Re: [Users] HA: Re: HA: Re: HA: Re: HP Integrated Lights Out
> 3
>
>
>
> ----- Original Message -----
> > From: "Dmitriy A Pyryakov" <DPyryakov(a)ekb.beeline.ru>
> > To: "Itamar Heim" <iheim(a)redhat.com>
> > Cc: users(a)ovirt.org
> > Sent: Thursday, September 20, 2012 9:59:34 AM
> > Subject: [Users] HA: Re: HA: Re: HA: Re: HP Integrated Lights Out
> > 3
> >
> >
> >
> >
> >
> >
> > I change Fedora 17 hosts to ovirt nodes (first - 2.5.0-2.0.fc17,
> > second -2.5.1-1.0.fc17). SPM on 2.5.0-2.0.fc17. ilo3 don't work.
> > In
> > vdsm.log now options presented.
>
> Can you paste here the call to fenceNode from the vdsm.log, thanks
Of course,
vdsm.log
Thread-1882::DEBUG::2012-09-20
09:02:52,920::API::1024::vds::(fenceNode)
fenceNode(addr=192.168.10.103,port=,agent=ipmilan,user=Administrator,passwd=XXXX,action=status,secure=,options=)
See, here in the PM Status command , options are empty in VDSM
Thread-1882::DEBUG::2012-09-20
09:02:53,951::API::1050::vds::(fenceNode) rc 1 in
agent=fence_ipmilan
ipaddr=192.168.10.103
login=Administrator
option=status
passwd=XXXX
out Getting status of IPMI:192.168.10.103...Chassis power = Unknown
Failed
err
engine.log:
2012-09-20 15:02:54,034 INFO
[org.ovirt.engine.core.bll.FencingExecutor] (ajp--0.0.0.0-8009-5)
Executing <Status> Power Management command, Proxy
Host:hyper1.ovirt.com, Agent:ipmilan, Target Host:, Management
IP:192.168.10.103, User:Administrator, Options:lanplus,power_wait=4
2012-09-20 15:02:54,056 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
(ajp--0.0.0.0-8009-5) START, FenceVdsVDSCommand(vdsId =
0a268762-02d7-11e2-b750-0011856cf23e, targetVdsId =
c57f5aa0-0301-11e2-8c67-0011856cf23e, action = Status, ip =
192.168.10.103, port = , type = ipmilan, user = Administrator,
password = ******, options = 'lanplus,power_wait=4'), log id:
5821013b
While we still see that engine sends those options correctly.
CCing Roy
Roy, it seems connected to the bug you had resolved but Dmitriy claims to have the right
vdsm with the fix , any ideas ?
> >BindingXMLRPC.py not found on proxy
> > host in /usr/share/vdsm. Only BindingXMLRPC.pyc file. Itamar Heim
> > <iheim(a)redhat.com> написано 14.09.2012 13:46:35:
> >
> > > От: Itamar Heim <iheim(a)redhat.com>
> > > Кому: Darrell Budic <darrell.budic(a)bigwells.net>
> > > Копия: Dmitriy A Pyryakov <DPyryakov(a)ekb.beeline.ru>,
> > > users(a)ovirt.org
> > > Дата: 14.09.2012 13:46
> > > Тема: Re: [Users] HA: Re: HA: Re: HP Integrated Lights Out 3
> > >
> > > On 09/14/2012 02:32 AM, Darrell Budic wrote:
> > > > That fix worked for me (ipmilan wise, anyway. Still no go on
> > > > ilo,
> > > > but we
> > > > knew that, right?). Thanks Itamar!
> > > >
> > > > Dmitriy, make sure you do this to all your host nodes, it may
> > > > run
> > > > the
> > > > test from any of them. You'll also want to be sure you delete
> > > > /usr/share/vdsm/BindingXMLRPC.pyc and .pyo, otherwise the
> > > > compiled
> > > > python is likely to still get used. Finally, I did need to
> > > > restart vdsmd
> > > > on all my nodes, "service vdsmd restart" on my Centos 6.3
> > > > system.
> > > > Glad
> > > > to know you can do that without causing problems for running
> > > > vms.
> > > >
> > > > I did notice that the ovirt management GUI still shows 3
> > > > Alerts
> > > > in the
> > > > alert area, and they are all "Power Management test
failed"
> > > > errors dated
> > > > from the first time their particular node was added to the
> > > > cluster. This
> > > > is even after restarting a vdsmd again and seeing Host xxx
> > > > power
> > > > management was verified successfully." in the event log.
> > >
> > > because the engine doesn't go and run 'test power management'
> > > all
> > > the
> > > time...
> > > click edit host, power management tab, click 'test'.
> > >
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >