[ClusterLabs] Antw: [EXT] Failed 'virsh' call when test RA run by crm_resource (con't)

[Ulrich Windl]

>>> Madison Kelly <mkelly at alteeve.com> schrieb am 12.01.2023 um 05:10 in Nachricht
<d156054e-6e5b-eb72-bf08-2155d34b9484 at alteeve.com>:
> Hi all,
> 
>    There was a lot of sub-threads, so I figured it's helpful to start a 
> new thread with a summary so far. For context; I have a super simple 
> perl script that pretends to be an RA for the sake of debugging.
> 
> https://pastebin.com/9z314TaB 

One thing I noticed: When "opening" a pipe, checking the "close" status is sometimes even more important than checking the open status; you don't check the close status...


> 
>    I've had variations log environment variables and confirmed that all 
> the variables in the direct call that work are in the crm_resource 
> triggered call. There are no selinux issues logged in audit.log and 
> selinux is permissive. The script logs the real and effective UID and 
> GID and it's the same in both instances. Calling other shell programs 
> (tested with 'hostname') run fine, this is specifically crm_resource -> 
> test RA -> virsh call.
> 
>    I ran strace on the virsh call from inside my test script (changing 
> 'virsh.good' to 'virsh.bad' between running directly and via 
> crm_resource. The strace runs made six files each time. Below are 
> pastebin links with the outputs of the six runs in one paste, but each 
> file's output is in it's own block (search for file: to see the 
> different file outputs)
> 
> Good/direct run of the test RA:
> - https://pastebin.com/xtqe9NSG 
> 
> Bad/crm_resource triggered run of the test RA:
> - https://pastebin.com/vBiLVejW 
> 
> Still absolutely stumped.
> 
> -- 
> Madison Kelly
> Alteeve's Niche!
> Chief Technical Officer
> c: +1-647-471-0951
> https://alteeve.com/ 
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users 
> 
> ClusterLabs home: https://www.clusterlabs.org/