Hi Slava,

do you have at least one another host in the same cluster or DC which doesn't have connection issues (in status Up or Maintenance)?

If so, please turn on debug logging for power management part using following command:

    /usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh --controller=127.0.0.1:8706 --connect --user=admin@internal

and enter following inside jboss-cli command prompt:

    /subsystem=logging/logger=org.ovirt.engine.core.bll.pm:add
    /subsystem=logging/logger=org.ovirt.engine.core.bll.pm:write-attribute(name=level,value=DEBUG)

    quit

Afterwards you will see more details in engine.log why other hosts were rejected during fence proxy selection process.

Btw above debug log changes are not permanent, they will be reverted on ovirt-engine restart or using following command:

    /usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh --controller=127.0.0.1:8706 --connect --user=admin@internal '/subsystem=logging/logger=org.ovirt.engine.core.bll.pm:remove'

Regards

Martin Perina

On Thu, Jan 12, 2017 at 4:42 PM, Slava Bendersky <volga629@networklab.ca> wrote:

Hello Everyone,

I need help with this error. What possible missing or miss-configured  ?

2017-01-12 05:17:31,444 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-38) [] Can not run fence action on host 'hosted_engine_1', no suitable proxy host was found

I tried from shell on host and it works fine.

Right now settings default dc, cluster from PM proxy definition.

Slava.

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users