2:33 a.m.
Trying to configure power management for a certain host and fence agent
always fail when I'm pressing Test button.
At the same time from command line on the same host all looks good:
[root@ovirt ~]# fence_ipmilan -a 172.16.22.1 -l user -p pwd -o status -v -P
Executing: /usr/bin/ipmitool -I lanplus -H 172.16.22.1 -p 623 -U user -P
pwd -L ADMINISTRATOR chassis power status
0 Chassis Power is on
Status: ON
[root@ovirt ~]#
What could be the reason?
Regards,
Artem
2:52 a.m.
Hi,
could you please provide engine logs so we can investigate?
Thanks
Martin
On Tue, Nov 14, 2017 at 9:33 AM, Artem Tambovskiy <
artem.tambovskiy(a)gmail.com> wrote:
Trying to configure power management for a certain host and fence
agent
always fail when I'm pressing Test button.
At the same time from command line on the same host all looks good:
[root@ovirt ~]# fence_ipmilan -a 172.16.22.1 -l user -p pwd -o status -v
-P
Executing: /usr/bin/ipmitool -I lanplus -H 172.16.22.1 -p 623 -U user -P
pwd -L ADMINISTRATOR chassis power status
0 Chassis Power is on
Status: ON
[root@ovirt ~]#
What could be the reason?
Regards,
Artem
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
3:10 a.m.
Hi,
In the engine.log appears following:
2017-11-14 12:04:33,081+03 ERROR
[org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-184)
[32fe1ce0-2e25-4e2e-a6bf-59f39a65b2f1] Can not run fence action on host
'ovirt.prod.env', no suitable proxy host was found.
2017-11-14 12:04:36,534+03 INFO
[org.ovirt.engine.core.bll.hostdeploy.UpdateVdsCommand] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Running command: UpdateVdsCommand
internal: false. Entities affected : ID:
a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d Type: VDSAction group
EDIT_HOST_CONFIGURATION with role type ADMIN
2017-11-14 12:04:36,704+03 ERROR
[org.ovirt.engine.core.bll.pm.FenceProxyLocator] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Can not run fence action on host
'ovirt.prod.env', no suitable proxy host was found.
2017-11-14 12:04:36,705+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,705+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,705+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,705+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,720+03 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
VDS_ALERT_PM_HEALTH_CHECK_START_MIGHT_FAIL(9,010), Correlation ID: null,
Call Stack: null, Custom Event ID: -1, Message: Health check on Host
<UNKNOWN> indicates that future attempts to Start this host using
Power-Management are expected to fail.
2017-11-14 12:04:36,720+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,720+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,720+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,720+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogableBase]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,731+03 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
VDS_ALERT_PM_HEALTH_CHECK_STOP_MIGHT_FAIL(9,011), Correlation ID: null,
Call Stack: null, Custom Event ID: -1, Message: Health check on Host
<UNKNOWN> indicates that future attempts to Stop this host using
Power-Management are expected to fail.
2017-11-14 12:04:36,765+03 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
KDUMP_DETECTION_NOT_CONFIGURED_ON_VDS(617), Correlation ID: null, Call
Stack: null, Custom Event ID: -1, Message: Kdump integration is enabled for
host ovirt.prod.env, but kdump is not configured properly on host.
2017-11-14 12:04:36,781+03 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
USER_UPDATE_VDS(43), Correlation ID: d83ce46d-ce89-4804-aba1-761103e93e8c,
Call Stack: null, Custom Event ID: -1, Message: Host ovirt.prod.env
configuration was updated by arta00@internal-authz.
Just let me know if more logs are needed.
Regards,
Artem
On Tue, Nov 14, 2017 at 11:52 AM, Martin Perina <mperina(a)redhat.com> wrote:
Hi,
could you please provide engine logs so we can investigate?
Thanks
Martin
On Tue, Nov 14, 2017 at 9:33 AM, Artem Tambovskiy <
artem.tambovskiy(a)gmail.com> wrote:
> Trying to configure power management for a certain host and fence agent
> always fail when I'm pressing Test button.
>
> At the same time from command line on the same host all looks good:
>
> [root@ovirt ~]# fence_ipmilan -a 172.16.22.1 -l user -p pwd -o status -v
> -P
> Executing: /usr/bin/ipmitool -I lanplus -H 172.16.22.1 -p 623 -U user -P
> pwd -L ADMINISTRATOR chassis power status
>
> 0 Chassis Power is on
>
> Status: ON
> [root@ovirt ~]#
>
> What could be the reason?
>
> Regards,
> Artem
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
--
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
3:29 a.m.
On Tue, Nov 14, 2017 at 10:10 AM, Artem Tambovskiy <
artem.tambovskiy(a)gmail.com> wrote:
Hi,
In the engine.log appears following:
2017-11-14 12:04:33,081+03 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator]
(default task-184) [32fe1ce0-2e25-4e2e-a6bf-59f39a65b2f1] Can not run
fence action on host 'ovirt.prod.env', no suitable proxy host was found.
Above is the important message, you don't have any other host which could
execute fence action. You need to have at least one other host in status Up
to be able to perform fence action.
2017-11-14 12:04:36,534+03 INFO
[org.ovirt.engine.core.bll.hostdeploy.UpdateVdsCommand]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Running
command: UpdateVdsCommand internal: false. Entities affected : ID:
a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d Type: VDSAction group
EDIT_HOST_CONFIGURATION with role type ADMIN
2017-11-14 12:04:36,704+03 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator]
(default task-186) [d83ce46d-ce89-4804-aba1-761103e93e8c] Can not run
fence action on host 'ovirt.prod.env', no suitable proxy host was found.
2017-11-14 12:04:36,705+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,705+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,705+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,705+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,720+03 WARN [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogDirector] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
VDS_ALERT_PM_HEALTH_CHECK_START_MIGHT_FAIL(9,010), Correlation ID: null,
Call Stack: null, Custom Event ID: -1, Message: Health check on Host
<UNKNOWN> indicates that future attempts to Start this host using
Power-Management are expected to fail.
2017-11-14 12:04:36,720+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,720+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error: null
2017-11-14 12:04:36,720+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,720+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogableBase] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] Failed to get vds
'a9bb1c6f-b9c9-4dc3-a24e-b83b2004552d', error null
2017-11-14 12:04:36,731+03 WARN [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogDirector] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
VDS_ALERT_PM_HEALTH_CHECK_STOP_MIGHT_FAIL(9,011), Correlation ID: null,
Call Stack: null, Custom Event ID: -1, Message: Health check on Host
<UNKNOWN> indicates that future attempts to Stop this host using
Power-Management are expected to fail.
2017-11-14 12:04:36,765+03 WARN [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogDirector] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID:
KDUMP_DETECTION_NOT_CONFIGURED_ON_VDS(617),
Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Kdump
integration is enabled for host ovirt.prod.env, but kdump is not configured
properly on host.
2017-11-14 12:04:36,781+03 INFO [org.ovirt.engine.core.dal.
dbbroker.auditloghandling.AuditLogDirector] (default task-186)
[d83ce46d-ce89-4804-aba1-761103e93e8c] EVENT_ID: USER_UPDATE_VDS(43),
Correlation ID: d83ce46d-ce89-4804-aba1-761103e93e8c, Call Stack: null,
Custom Event ID: -1, Message: Host ovirt.prod.env configuration was updated
by arta00@internal-authz.
Just let me know if more logs are needed.
Regards,
Artem
On Tue, Nov 14, 2017 at 11:52 AM, Martin Perina <mperina(a)redhat.com>
wrote:
> Hi,
>
> could you please provide engine logs so we can investigate?
>
> Thanks
>
> Martin
>
>
> On Tue, Nov 14, 2017 at 9:33 AM, Artem Tambovskiy <
> artem.tambovskiy(a)gmail.com> wrote:
>
>> Trying to configure power management for a certain host and fence agent
>> always fail when I'm pressing Test button.
>>
>> At the same time from command line on the same host all looks good:
>>
>> [root@ovirt ~]# fence_ipmilan -a 172.16.22.1 -l user -p pwd -o status
>> -v -P
>> Executing: /usr/bin/ipmitool -I lanplus -H 172.16.22.1 -p 623 -U user -P
>> pwd -L ADMINISTRATOR chassis power status
>>
>> 0 Chassis Power is on
>>
>> Status: ON
>> [root@ovirt ~]#
>>
>> What could be the reason?
>>
>> Regards,
>> Artem
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
> Martin Perina
> Associate Manager, Software Engineering
> Red Hat Czech s.r.o.
>
--
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
3:06 a.m.
On Tue, Nov 14, 2017 at 9:33 AM, Artem Tambovskiy <
artem.tambovskiy(a)gmail.com> wrote:
Trying to configure power management for a certain host and fence
agent
always fail when I'm pressing Test button.
At the same time from command line on the same host all looks good:
[root@ovirt ~]# fence_ipmilan -a 172.16.22.1 -l user -p pwd -o status -v
-P
Executing: /usr/bin/ipmitool -I lanplus -H 172.16.22.1 -p 623 -U user -P
pwd -L ADMINISTRATOR chassis power status
0 Chassis Power is on
Status: ON
[root@ovirt ~]#
What could be the reason?
Regards,
Artem
What do you put in options line of the configuration window for power mgmt
when you test?
In my case with Dell M610 blades, it works with ipmilan agent and setting
this
privlvl=operator,lanplus=on
I think in your case you need at least "lanplus=on" that shouldn't be the
default of the command executed.
I see that your command line seems to expand in "-L ADMINISTRATOR".
In my case in iDRAC for the blade I have configured my dedicate fencing
user with privilege capped to operator
HIH,
Gianluca
3:31 a.m.
On Tue, Nov 14, 2017 at 10:06 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com
wrote:
> On Tue, Nov 14, 2017 at 9:33 AM, Artem Tambovskiy <
> artem.tambovskiy(a)gmail.com wrote:
>
>> Trying to configure power management for a certain host and fence agent
>> always fail when I'm pressing Test button.
>>
>> At the same time from command line on the same host all looks good:
>>
>> [root@ovirt ~]# fence_ipmilan -a 172.16.22.1 -l user -p pwd -o status -v
>> -P
>> Executing: /usr/bin/ipmitool -I lanplus -H 172.16.22.1 -p 623 -U user -P
>> pwd -L ADMINISTRATOR chassis power status
>>
>> 0 Chassis Power is on
>>
>> Status: ON
>> [root@ovirt ~]#
>>
>> What could be the reason?
>>
>> Regards,
>> Artem
>>
>>
>>
>>
> What do you put in options line of the configuration window for power mgmt
> when you test?
>
> In my case with Dell M610 blades, it works with ipmilan agent and setting
> this
>
> privlvl=operator,lanplus=on
>
> I think in your case you need at least "lanplus=on" that shouldn't be
the
> default of the command executed.
>
lanplus=1 is the default for ipmilan fence agent, no need to specify in
Options
I see that your command line seems to expand in "-L ADMINISTRATOR".
In my case in iDRAC for the blade I have configured my dedicate fencing
user with privilege capped to operator
HIH,
Gianluca
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
2364
days inactive
2364
days old
5 comments
3 participants
participants (3)
-
Artem Tambovskiy -
Gianluca Cecchi -
Martin Perina