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.
DescriptionMichal Mazourek
2021-04-27 14:58:03 UTC
Description of problem:
As shown in bz1952140, it's easy to create fence_sbd agent with misconfiguration (e.g. with invalid device id). It would be helpful to prevent this situation, either on pcs side by validating the parameters when creating the agent or on fence-agent side by self-validation.
Version-Release number of selected component (if applicable):
pcs-0.10.8-1.el8
How reproducible:
always
Steps to Reproduce:
## create fence_sbd agent with invalid disk id
[root@virt-023 ~]# pcs stonith create sbd_agent fence_sbd devices=invalidId
[root@virt-023 ~]# echo $?
0
[root@virt-023 ~]# pcs stonith status
* sbd_agent (stonith:fence_sbd): Stopped
Actual results:
The agent is stopped without any parameter check or an error message on output. There is 'Failed Resource Action' in cluster status, but without any visible exit reason:
> * sbd_agent_start_0 on virt-023 'error' (1): call=29, status='complete', exitreason='', last-rc-change='2021-04-27 14:24:45 +02:00', queued=0ms, exec=1131ms
The reason is correctly shown in /var/log/messages:
> Apr 27 15:33:05 virt-023 /fence_sbd[1251019]: "invalidId" does not exist
> Apr 27 15:33:06 virt-023 pacemaker-fenced[1235563]: notice: fence_sbd_monitor_1[1251019] error output [ 2021-04-27 15:33:05,992 ERROR: "invalidId" does not exist ]
Expected results:
The agent's parameters are validated.
Additional info:
As this is probably not a high-priority issue right now, it is not expected to have this function in RHEL8 time frame.
This originates from bz1952140 comment 2.
It has been already decided that pcs will not implement validations for fence and resource agents options. Those validations must be done by the agents themselves. We already do have BZs requesting support for calling the validation from pcs.
> There is 'Failed Resource Action' in cluster status, but without any visible exit reason
I guess that's because fence_sbd doesn't provide any exit reason. Pcs can do nothing about it.
*** This bug has been marked as a duplicate of bug 1816852 ***