Bug 2127113

Summary: fence_scsi instance attributes validation via stonith_admin always fails
Product: Red Hat Enterprise Linux 9 Reporter: Ondrej Mular <omular>
Component: fence-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED MIGRATED QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.1CC: cluster-maint
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 19:50:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2112270, 2112271    

Description Ondrej Mular 2022-09-15 11:44:56 UTC
Description of problem:
Instance attributes validation of fence_scsi agent via stonith_admin always fails. The problem is with validation of the ‘plug’ option which is required by the agent. Even the explicitly specified ‘plug’ or ‘pcmk_host_list’ options doesn’t help. From pcs point of view, stonith_admin should handle all of these cases as they are a valid configuration.

Version-Release number of selected component (if applicable):
[root@rhel91-devel1 pcs]# rpm -q pacemaker fence-agents-scsi
pacemaker-2.1.4-5.el9.x86_64
fence-agents-scsi-4.10.0-30.el9.noarch


How reproducible:
always

Steps to Reproduce:
Note: all commands are executed on a single node cluster with node name ’localhost’.
[root@rhel91-devel1 pcs]# /usr/sbin/stonith_admin --validate --agent fence_scsi
Validation of fence_scsi failed
2022-09-15 11:25:16,694 ERROR: Failed: unable to parse output of corosync-cmapctl or node does not exist

2022-09-15 11:25:16,695 ERROR: Please use '-h' for usage


[root@rhel91-devel1 pcs]# echo $?
1
[root@rhel91-devel1 pcs]# /usr/sbin/stonith_admin --validate --agent fence_scsi --option pcmk_host_list=localhost
Validation of fence_scsi failed
2022-09-15 11:26:02,022 ERROR: Failed: unable to parse output of corosync-cmapctl or node does not exist

2022-09-15 11:26:02,022 ERROR: Please use '-h' for usage


[root@rhel91-devel1 pcs]# echo $?
1
[root@rhel91-devel1 pcs]# /usr/sbin/stonith_admin --validate --agent fence_scsi --option plug=localhost
Validation of fence_scsi failed
2022-09-15 11:26:16,965 ERROR: Failed: unable to parse output of corosync-cmapctl or node does not exist

2022-09-15 11:26:16,966 ERROR: Please use '-h' for usage


[root@rhel91-devel1 pcs]# echo $?
1
[root@rhel91-devel1 pcs]# corosync-cmapctl | grep localhost
nodelist.node.0.name (str) = localhost
nodelist.node.0.ring0_addr (str) = localhost
totem.interface.0.bindnetaddr (str) = localhost


Actual results:
Validation fails


Expected results:
Successful validation

Additional info:
Running just agent itself works ok:
[root@rhel91-devel1 pcs]# fence_scsi -o validate-all --plug non-existing-node; echo $?
2022-09-15 12:44:54,360 ERROR: Failed: unable to parse output of corosync-cmapctl or node does not exist

2022-09-15 12:44:54,360 ERROR: Please use '-h' for usage

1
[root@rhel91-devel1 pcs]# fence_scsi -o validate-all --plug localhost; echo $?
0

From this snippet of strace output I assume that this is written to stdin of agent for validation:
[root@rhel91-devel1 pcs]# strace /usr/sbin/stonith_admin --validate --agent fence_scsi --option plug=localhost
<snip>
write(8, "nodename=node1\n", 15)        = 15
write(8, "action=validate-all\n", 20)   = 20
write(8, "port=node1\n", 11)            = 11
write(8, "plug=localhost\n", 15)        = 15
<snip>

So I tried to execute agent with the same stdin and indeed it fails with the same error:
[root@rhel91-devel1 pcs]# echo -e "nodename=node1\naction=validate-all\nport=node1\nplug=localhost\n" | fence_scsi; echo $?
2022-09-15 13:01:36,710 ERROR: Failed: unable to parse output of corosync-cmapctl or node does not exist

2022-09-15 13:01:36,710 ERROR: Please use '-h' for usage

1
However, validation passes after removing “nodename=node1” from stdin, even though the “nodename” should not be accepted by the agent according to its man page.
[root@rhel91-devel1 pcs]# echo -e "action=validate-all\nport=node1\nplug=localhost\n" | fence_scsi; echo $?
0

I didn’t try any other agent but I would guess that other agents may be affected as well.

Comment 1 Ken Gaillot 2022-09-15 15:25:37 UTC
This sounds like something the agent's doing. At the least its documentation doesn't seem to match what options are actually accepted

If the main problem is that the target should be passed via "plug", then pcmk_host_argument=plug might help. Note that pacemaker will check the metadata and use port if advertised, otherwise plug if advertised, so this could be a metadata issue.

Comment 2 Ondrej Mular 2022-09-16 06:50:40 UTC
Well, pcmk_host_argument=plug doesn't solve anything because stonith_admin then sends "plug=node1" to the agent instead of real node name. I assume that the agent is checking plug value against node list from corosync, which is not an unreasonable check. But this check always fails as it gets a dummy node name from stonith_admin. If stonith_admin would send a real node name in 'nodename' option, fence_scsi validation will be successful.

So I can see 2 options to fix this:
 * stonith_admin should send real node names to agent when running 'validate-all' action
 * agents should not check if plug (or port or however it's called in other agents) is a real cluster node

Comment 3 Oyvind Albrigtsen 2022-09-22 07:39:29 UTC
nodename is supported for backwards compatibility:
https://github.com/ClusterLabs/fence-agents/blob/8b0ea39d49453c284d6ae708ec5f14c2bf867780/agents/scsi/fence_scsi.py#L560-L563

It's help text have been removed, so it's not advertised in manpage/metadata.

Comment 5 RHEL Program Management 2023-09-22 19:49:06 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-22 19:50:51 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.