If WTI device expects login and login name is not entered then it fails with traceback. Correct error message is expected. Login name is required for WTI, so it has to be checked after login is encountered.
Same problem can occur with password (also optional on wti)
Fixed in: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commit;h=6442d9f60e650fc6669e6422207f27a073aca8ac
Created attachment 359277 [details] Proposed patch Similar problem exists also for APC
Final patch: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commit;h=0b53674b0634755fe041e6e8fbd00780ca5c8791
[root@z2 ~]# echo -e "ipaddr=1.1.1.1\nport=44\nipport=54444\n" | fence_apc Failed: You have to set login name [root@z2 ~]# echo -e "ipaddr=1.1.1.1\nport=44\nipport=54444\nlogin=x\n" | fence_apc Failed: You have to enter password or password script fence_apc clearly still requires both login and password to start any operation. Is this as intended?
(In reply to comment #10) > [root@z2 ~]# echo -e "ipaddr=1.1.1.1\nport=44\nipport=54444\n" | fence_apc > Failed: You have to set login name > > [root@z2 ~]# echo -e "ipaddr=1.1.1.1\nport=44\nipport=54444\nlogin=x\n" | > fence_apc > Failed: You have to enter password or password script > > fence_apc clearly still requires both login and password to start any > operation. Is this as intended? Yes. username/password is required. This bug wasn't about username/password not being required. It was that when username/password wasn't given to fence_wti, the fence agent would fail in a non graceful manner. As you can see, the apc fence agent is failing in a graceful manner and prompting the user for the username/password as appropriate Did you check the WTI agent specifically to make sure that the traceback is gone?
APC fencing devices always require username and password. WTI fencing devices usually require both. Older devices such as the IPS may get by with only the password.
that is: the fence_wti agent should not _require_ a username, only a password. APC should require both.
> fence_apc clearly still requires both login and password to start any > operation. Is this as intended? Yeah, that's correct behavior for fence_apc.
the wti agent worked as expected, so if the apc case is also as it should be, I'm marking this as verified. Thanks for comments.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0266.html