[ovirt-users] fence_rhevm and ovirt 4.2

Hello, I'm configuring a virtual rhcs cluster and would like to use fence_rhevm agent for stonith. As VMs composing the 4-nodes cluster I'm using CentOS 7.4 os with fence-agents-rhevm-4.0.11-66.el7_4.4.x86_64; I see that in 7.5 the agent is fence-agents-rhevm-4.0.11-86.el7_5.2.x86_64 but with no modification for the /usr/sbin/fence_rhevm python script apart the BUILD_DATE line. Some questions: - it seems it is still in API v3 even if deprecated; any particular reason? Possible to update to V4? Can I create a RFE bugzilla? This is in fact what I get in engine events registering connection: Client from address "10.4.4.68" is using version 3 of the API, which has been deprecated since version 4.0 of the engine, and will no longer be supported starting with version 4.3. Make sure to update that client to use a supported versions of the API and the SDKs, before upgrading to version 4.3 of the engine. 7/7/184:56:11 PM User fenceuser@internal-authz connecting from '10.4.4.68' using session 'OVgdzMofRFDS4ZKSdL83mRyGUFEdc+++onJHzGiAfpYuS07xa/EbBqFEPtztpwEeRzCn9mBOTGXE69rBbHlhXQ==' logged in. 7/7/184:56:11 PM - UserRole ok Back in April 2017 for version 4.1.1 I had problems and it seems I had to set super user privileges for the "fencing user" See thread here https://lists.ovirt.org/archives/list/users@ovirt.org/message/FS5YFU5ZXIY... Now instead I only set UserRole for the defined "fenceuser" on the virtual cluster VMS and it works ok - for a VM with permissions already setup: [root@cl1 ~]# fence_rhevm -a 10.4.192.49 -l "fenceuser@internal" -S /usr/local/bin/pwd_ovmgr01.sh -z --ssl-insecure -o status --shell-timeout=20 --power-wait=10 -n cl1 Status: ON - for a VM still without permissions [root@cl1 ~]# fence_rhevm -a 10.4.192.49 -l "fenceuser@internal" -S /usr/local/bin/pwd_ovmgr01.sh -z --ssl-insecure -o status --shell-timeout=20 --power-wait=10 -n cl2 Failed: Unable to obtain correct plug status or plug is not available - for a VM with permissions already setup: I'm able to make power off / power on of the VM Thanks, Gianluca