The same issue as described in bz2039399 is present again:

(bz2039399 comment #0)
> Description of problem:
> When removing pacemaker_remote node from cluster configuration (via 'pcs
> cluster node remove-remote'), fence action occurs on the remote node.
> 
> 
> How reproducible:
> always
> 
> 
> Steps to Reproduce:
> [root@virt-255 ~]# pcs status
> Cluster name: STSRHTS22418
> Cluster Summary:
>   * Stack: corosync
>   * Current DC: virt-256 (version 2.1.2-1.el9-ada5c3b36e2) - partition with
> quorum
>   * Last updated: Tue Jan 11 15:29:56 2022
>   * Last change:  Tue Jan 11 15:29:01 2022 by root via cibadmin on virt-255
>   * 4 nodes configured
>   * 4 resource instances configured
> 
> Node List:
>   * Online: [ virt-255 virt-256 virt-261 virt-262 ]
> 
> Full List of Resources:
>   * fence-virt-255	(stonith:fence_xvm):	 Started virt-255
>   * fence-virt-256	(stonith:fence_xvm):	 Started virt-256
>   * fence-virt-261	(stonith:fence_xvm):	 Started virt-261
>   * fence-virt-262	(stonith:fence_xvm):	 Started virt-262
> 
> Daemon Status:
>   corosync: active/disabled
>   pacemaker: active/disabled
>   pcsd: active/enabled
> 
> [root@virt-255 ~]# pcs cluster node remove virt-262
> Destroying cluster on hosts: 'virt-262'...
> virt-262: Successfully destroyed cluster
> Sending updated corosync.conf to nodes...
> virt-261: Succeeded
> virt-255: Succeeded
> virt-256: Succeeded
> virt-255: Corosync configuration reloaded
> 
> [root@virt-255 ~]# pcs cluster node add-remote virt-262
> No addresses specified for host 'virt-262', using 'virt-262'
> Sending 'pacemaker authkey' to 'virt-262'
> virt-262: successful distribution of the file 'pacemaker authkey'
> Requesting 'pacemaker_remote enable', 'pacemaker_remote start' on 'virt-262'
> virt-262: successful run of 'pacemaker_remote enable'
> virt-262: successful run of 'pacemaker_remote start'
> 
> [root@virt-255 ~]# pcs status | grep "Node List" -A 2
> Node List:
>   * Online: [ virt-255 virt-256 virt-261 ]
>   * RemoteOnline: [ virt-262 ]
> 
> ## removing the remote node
> 
> [root@virt-255 ~]# pcs cluster node remove-remote virt-262
> Requesting 'pacemaker_remote disable', 'pacemaker_remote stop' on 'virt-262'
> virt-262: successful run of 'pacemaker_remote disable'
> virt-262: successful run of 'pacemaker_remote stop'
> Requesting remove 'pacemaker authkey' from 'virt-262'
> virt-262: successful removal of the file 'pacemaker authkey'
> Deleting Resource - virt-262
> [root@virt-255 ~]# echo $?
> 0
> 
> > This will stuck on 'Deleting Resource - virt-262' line for a few minutes, fence of the remote node will happen after that.
> 
> 
> Actual results:
> [root@virt-255 ~]# pcs stonith history
> reboot of virt-262 successful: delegate=virt-261,
> client=pacemaker-controld.439906, origin=virt-256, completed='1970-01-05
> 01:18:46 +01:00'
> 1 event found
> 
> 
> Expected results:
> No fence action will occur


Note:
After running "pcs cluster node remove-remote {node}", sometimes the command ends up in a timeout error (probably when the fence happens before the command ends) and sometimes it finishes successfully, however the fence action on the remote node happens every time.

Versions:
Found in pacemaker-2.1.5-4 (both on RHEL8 and RHEL9).
After examination, the issue is first present in pacemaker-2.1.5-1 (it is working fine in pacemaker-2.1.4-5).