Document OSX solution for OSX fork safety issue

[gmuloc]

When running validate state or cv deploy on OSX the following error can occur:

TASK [arista.avd.cv_deploy : Deploy device configurations and tags to CloudVision] *************************************************************************************************************
Wednesday 05 February 2025  20:56:27 -0500 (0:00:00.036)       0:00:05.714 **** 
Wednesday 05 February 2025  20:56:27 -0500 (0:00:00.036)       0:00:05.714 **** 
objc[54680]: +[NSMutableString initialize] may have been in progress in another thread when fork() was called.
objc[54680]: +[NSMutableString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
ERROR! A worker was found in a dead state

The solution is to use

export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

[ClausHolbechArista]

It is already documented in Ansible documentation.

[gmuloc]

it is but we are getting the question on a weekly basis in various channels