Bug 987446

Created attachment 782866 [details]
vdsm + engine logs, local env

Verification failed on sf19:

1) secure = no, nothing happens


Thread-1826::DEBUG::2013-08-05 17:36:41,579::API::1094::vds::(fenceNode) rc 0 in agent=fence_apc_snmp
ipaddr=10.35.23.24
login=talayan
option=status
passwd=XXXX
port=4
secure=no out Status: ON
 err Parse error: Ignoring unknown option 'secure=no'

Thread-1827::DEBUG::2013-08-05 17:36:41,584::API::1068::vds::(fenceNode) fenceNode(addr=10.35.23.24,port=,agent=apc_snmp,user=talayan,passwd=XXXX,action=status,secure=,options=port=4
secure=no)
Thread-1827::DEBUG::2013-08-05 17:36:41,957::API::1094::vds::(fenceNode) rc 0 in agent=fence_apc_snmp
ipaddr=10.35.23.24
login=talayan
option=status
passwd=XXXX
port=4
secure=no out Status: ON
 err Parse error: Ignoring unknown option 'secure=no'

2) secure = yes, icon change to rebooting for a few seconds - host is not rebooted

Thread-1916::DEBUG::2013-08-05 17:38:16,752::API::1094::vds::(fenceNode) rc 0 in agent=fence_apc_snmp
ipaddr=10.35.23.24
login=talayan
option=status
passwd=XXXX
port=4
secure=yes out Status: ON
 err Parse error: Ignoring unknown option 'secure=yes'

Thread-1917::DEBUG::2013-08-05 17:38:16,757::API::1068::vds::(fenceNode) fenceNode(addr=10.35.23.24,port=,agent=apc_snmp,user=talayan,passwd=XXXX,action=status,secure=,options=port=4
secure=yes)
Thread-1917::DEBUG::2013-08-05 17:38:17,098::API::1094::vds::(fenceNode) rc 0 in agent=fence_apc_snmp
ipaddr=10.35.23.24
login=talayan
option=status
passwd=XXXX
port=4
secure=yes out Status: ON
 err Parse error: Ignoring unknown option 'secure=yes'

(In reply to Barak Dagan from comment #2)

Can you please check that you succeeded to push the TEST button and get the status OK
I don't understand why guessing the secure flag , you should know it and it totally dependant in the specific engine you are testing 
Please try to verify again doing the exect scenarion as in the bug description :

Add host, add primary and secondary agents of power management, check via test button if agents defined correct. Check concurrent option and try to restart host.

If TEST is not working, there is no point in going further, please fix that 
Also , you will probably have to test on a diffrent agent rather than APC due to 
BZ 982266

Please let me know if you think this BZ should be dependant on BZ 982266

(In reply to Eli Mesika from comment #4)
> (In reply to Barak Dagan from comment #2)
> 
> Can you please check that you succeeded to push the TEST button and get the
> status OK
> I don't understand why guessing the secure flag , you should know it and it
> totally dependant in the specific engine you are testing 
> Please try to verify again doing the exect scenarion as in the bug
> description :
> 
> Add host, add primary and secondary agents of power management, check via
> test button if agents defined correct. Check concurrent option and try to
> restart host.
> 
> If TEST is not working, there is no point in going further, please fix that 
> Also , you will probably have to test on a diffrent agent rather than APC
> due to 
> BZ 982266
> 
> Please let me know if you think this BZ should be dependant on BZ 982266
rhevm sf19
hosts: vdsm-4.10.2-24.0.el6ev
one of host with two power managements apc_snmp and ipmilan
click on test button show "Test Succeeded, on"
Trying fence host:
Receive messages: Failed to stop Host aqua-vds7.qa.lab.tlv.redhat.com, (User: admin@internal).
Failed to restart Host aqua-vds7.qa.lab.tlv.redhat.com, (User: admin@internal).
In engine still null where proxie:
Executing <Stop> Power Management command, Proxy Host:null, Agent:ipmilan, Target Host:aqua-vds7.qa.lab.tlv.redhat.com, Management IP:aqua-vds7-mgmt.qa.lab.tlv.redhat.com, User:root, Options:

Please test with sf 19.1 , see attached image showing that this fix was not inclused in sf19 , only in sf19.1

Created attachment 784264 [details]
BZ is meregd only into sf19.1

Verified on SF 19.1

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1149.html