Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
I've moved this to RHEL7; RHEL6 is tech preview and if it is moved to supported it would be with some very limited validated usages, which would not include pacemaker.
Broader support would have to be considered for RHEL7. fence_sanlock is a bit peculiar, it isn't quite like other simplistic fence agents; I'm not sure how all the details would work in a pacemaker environment. We may have to add some new
restrictions/checks/caveats/etc.
As far as "monitor" goes, it's one of those things that may not make sense here.
As far as the agent args, I believe the agent currently specifies that in its
"metadata" output.