Current running engine build --> commit: 61c11aecc40e755d08b6c34c6fe1c0a07fa94de8 Host power management is having some issues: 2013-01-28 13:15:49,320 ERROR [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-11) Illegal value in PM Proxy Preferences string , skipped. 2013-01-28 13:15:49,321 ERROR [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-11) Failed to run Power Management command on Host , no running proxy Host was found. - DHC

On 01/28/2013 10:19 PM, Eli Mesika wrote: > ----- Original Message ----- >> From: "Dead Horse" <deadhorseconsulting(a)gmail.com&gt; >> To: &quot;&lt;users(a)ovirt.org&gt;&quot; <users(a)ovirt.org&gt; >> Sent: Monday, January 28, 2013 10:19:54 PM >> Subject: Re: [Users] host power managment failures >> >> >> >> >> Removing and re-adding the host then configuring power management >> resolves this. >> - DHC >> >> >> >> >> On Mon, Jan 28, 2013 at 1:25 PM, Dead Horse < >> deadhorseconsulting(a)gmail.com > wrote: >> >> >> >> >> Current running engine build --> commit: >> 61c11aecc40e755d08b6c34c6fe1c0a07fa94de8 >> >> Host power management is having some issues: >> >> 2013-01-28 13:15:49,320 ERROR >> [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-11) >> Illegal value in PM Proxy Preferences string , skipped. > Can you elaborate how did you got this? I suspect that maybe we have > a bug here > Having the same problem here. I installed the 3 nodes from iso and registered them to oVirt. In ovirt I approved them and added the Power Management settings. The source list is empty and Test fails with the message there is no other host to test it from. 2013-03-15 13:33:12,702 ERROR [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-6) Illegal value in PM Proxy Preferences string , skipped. 2013-03-15 13:33:12,708 ERROR [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-6) Failed to run Power Management command on Host , no running proxy Host was found. 2013-03-15 13:33:14,400 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-6) Unable to get value of property: pmSecondaryUser for class org.ovirt.engine.core.common.businessentities.VdsStatic 2013-03-15 13:33:14,413 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-6) Unable to get value of property: pmSecondaryUser for class org.ovirt.engine.core.common.businessentities.VdsStatic 2013-03-15 13:33:14,421 INFO [org.ovirt.engine.core.bll.UpdateVdsCommand] (ajp--127.0.0.1-8702-6) [724bd4e5] Running command: UpdateVdsCommand internal: false. Entities affected : ID: cfbbea9e-3986-4d8c-94db-a44f7a0bdc3e Type: VDS 2013-03-15 13:33:14,489 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-6) Unable to get value of property: pmSecondaryUser for class org.ovirt.engine.core.common.businessentities.VdsStatic 2013-03-15 13:33:14,497 WARN [org.ovirt.engine.core.compat.backendcompat.PropertyInfo] (ajp--127.0.0.1-8702-6) Unable to get value of property: pmSecondaryUser for class org.ovirt.engine.core.common.businessentities.VdsStatic 2013-03-15 13:33:15,370 ERROR [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-6) [724bd4e5] Illegal value in PM Proxy Preferences string , skipped. 2013-03-15 13:33:15,377 ERROR [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-6) [724bd4e5] Failed to run Power Management command on Host vh02-cl01-en01, no running proxy Host was found. Installing the node from ovirt with ssh appears to work ok, there I see as source cluster and dc to test it.

Jorick Astrego wrote: > >> >> Having the same problem here. I installed the 3 nodes from iso and >> registered them to oVirt. In ovirt I approved them and added the >> Power Management settings. The source list is empty and Test fails >> with the message there is no other host to test it from. >> >> 2 >> >> Installing the node from ovirt with ssh appears to work ok, there I >> see as source cluster and dc to test it. >> > > Just found out if I register the node and approve without power > management, I can then edit the node and enable/test powermanagent. > Approving the node and enabling power management at the same time > fails..... > If you try to register the FIRST node and try to set powermanagment then it will fail. Reason is because the check is done from another host in the cluster en since there is none it will error. Have been bitten by this multiple times when adding a host and thinking I could start adding a second before the first was ready. Adding a second and third in parallel when the first is ready should be no problem.