Bug 962088

Description of problem:
Currently unable to use fence_sanlock as an agent with pacemaker (1.1.8), RH fencing agent api not fully implemented (monitor, list etc)

Version-Release number of selected component (if applicable):
fence-sanlock-2.6-2.el6.x86_64

How reproducible:
Can be reproduced by attempting to use fence_sanlock as a stonith agent in pacemaker.

Steps to Reproduce:
1. CMAN running and using the pacemaker redirect fencing agent.

2. Pacemaker running (pacemaker-1.1.8-7.el6.x86_64), attempt to add a stonith device using the fence_sanlock agent (note that the host list, map and custom argument were included since fence_sanlock does not use the host name)
pcs stonith create st-sanlock fence_sanlock path="/dev/mapper/vg_shared-lv_sanlock" pcmk_host_list="hostname1 hostname2" pcmk_host_map="hostname1:1;hostname2:2" pcmk_host_argument="host_id

3. Check status of stonith device using pcs status and monitor logs
  
Actual results:
Device will be added to the running cib, but will fail as the monitor operation is not supported, from /var/log/messages;

May 10 01:33:42 hostname1 stonith-ng[10542]:  warning: log_operation: st-sanlock:10725 [ host_id argument required ]

Expected results:
Expectation had been that the provided fence_sanlock agent would be compatible with pacemaker.

Additional info:
I'd raised this on the pacemaker mailing list to see if anyone had previously used fence_sanlock with pacemaker, and whether it was intended to be used as such. I was requested to raise a ticket here.

Wasn't sure whether to raise this against the sanlock or fence-agents component, chose sanlock since its listed as the srpm for the fence-agent package

Thanks,
John