Bug 1359875 - Error "Failed: Unable to obtain correct plug status or plug is not available" When using RHEM Power management tool
Summary: Error "Failed: Unable to obtain correct plug status or plug is not available"...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Eli Mesika
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-25 15:13 UTC by emahoney
Modified: 2023-09-14 03:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-25 10:54:31 UTC
oVirt Team: Infra
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
Engine.log from manager (8.62 MB, text/plain)
2016-07-25 15:18 UTC, emahoney
no flags Details
Installed RPMs (67.75 KB, text/plain)
2016-07-26 14:06 UTC, emahoney
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1219620 0 unspecified CLOSED upgrade to oVirt 3.5.2 breaks power management (at least idrac7) 2021-02-22 00:41:40 UTC

Description emahoney 2016-07-25 15:13:53 UTC
Description of problem:
When I try the fencing tool on the CLI the results are as expected

>Executing: /usr/bin/ipmitool -I lanplus -H 192.168.198.208 -U zzzzrilo -P [set] -p 623 -L ADMINISTRATOR chassis power >status
>
>0 Chassis Power is on
>
>
>Status: ON

When I try the RHEVM Powermanagement tool, I get following error:

Failed: Unable to obtain correct plug status or plug is not available

vdsm.log on fencing_proxy machine:

jsonrpc.Executor/6::DEBUG::2016-07-12 15:10:12,709::task::993::Storage.TaskManager.Task::(_decref) Task=`d744754b-8954-4186-8054-3a52c9b8ad38`::ref 0 aborting False
jsonrpc.Executor/1::DEBUG::2016-07-12 15:10:12,876::API::1274::vds::(fenceNode) fenceNode(addr=192.168.198.208,port=,agent=ipmilan,user=zzzzrilo,passwd=********,action=status,secure=False,options=power_wait=
4
lanplus,policy=None)
jsonrpc.Executor/1::DEBUG::2016-07-12 15:10:12,876::utils::671::root::(execCmd) /usr/bin/taskset --cpu-list 0-15 /usr/sbin/fence_ipmilan (cwd None)
jsonrpc.Executor/1::DEBUG::2016-07-12 15:10:13,169::utils::689::root::(execCmd) FAILED: <err> = 'Failed: Unable to obtain correct plug status or plug is not available\n\n\n'; <rc> = 1
jsonrpc.Executor/1::DEBUG::2016-07-12 15:10:13,169::API::1229::vds::(fence) rc 1 inp agent=fence_ipmilan
ipaddr=192.168.198.208
login=zzzzrilo
action=status
passwd=XXXX
power_wait=4
lanplus out [] err ['Failed: Unable to obtain correct plug status or plug is not available', '', '']
jsonrpc.Executor/1::DEBUG::2016-07-12 15:10:13,170::API::1300::vds::(fenceNode) rc 1 in agent=fence_ipmilan
ipaddr=192.168.198.208
login=zzzzrilo
action=status
passwd=XXXX
power_wait=4
lanplus out [] err ['Failed: Unable to obtain correct plug status or plug is not available', '', '']

Version-Release number of selected component (if applicable):
fence-agents-4.0.15-12.el6.x86_64  
rhevm.noarch    3.5.8-0.1.el6ev                                      
rhevm-backend.noarch  3.5.8-0.1.el6ev 
rhevm-cli.noarch      3.5.0.6-1.el6ev
                         


How reproducible:
Every time on the customers hardware.
ProLiant DL385 G7 , with ilo3


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Seems very similar to https://bugzilla.redhat.com/show_bug.cgi?id=1219620

Comment 1 emahoney 2016-07-25 15:18:25 UTC
Created attachment 1183830 [details]
Engine.log from manager

Comment 2 Martin Perina 2016-07-26 07:40:05 UTC
Hmm, this should be solved in 3.5.4 by BZ1219620, Eli could you please take a look?

Comment 3 Eli Mesika 2016-07-26 08:36:56 UTC
please attach the result of the following query from psql prompt :

select * from fence_agents ;

Comment 4 Oved Ourfali 2016-07-26 12:13:22 UTC
Please also fill in the correct version in the bug.

Comment 5 emahoney 2016-07-26 14:06:46 UTC
Created attachment 1184282 [details]
Installed RPMs

Comment 7 emahoney 2016-07-26 14:15:04 UTC
Eli, in the dbdump, I do not see any relation named fence_agents...

[root@xxx tmp]# psql -U engine
psql (8.4.20)
Type "help" for help.

engine=> select * from fence_agents ;
ERROR:  relation "fence_agents" does not exist
LINE 1: select * from fence_agents ;
                      ^
engine=> \q
[root@xxx tmp]# psql -U postgres
psql (8.4.20)
Type "help" for help.

postgres=# select * from fence_agents ;
ERROR:  relation "fence_agents" does not exist
LINE 1: select * from fence_agents ;

Let me know if I am missing something.

-Mahoney

Comment 8 Eli Mesika 2016-07-26 15:04:32 UTC
workaround for this to work in 3.5.3 is to put "lanplus=1" instead pf "lanplus" in the options field , then save and test again

Comment 9 Oved Ourfali 2016-07-27 08:21:11 UTC
Closing as duplicate.
Please apply what's written in Comment 8.

Comment 12 Red Hat Bugzilla 2023-09-14 03:28:36 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.