Closed fishfacemcgee closed 1 year ago
Files identified in the description: None
If these files are inaccurate, please update the component name
section of the description or use the !component
bot command.
After doing some additional triage, I've confirmed that the OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
environment variable has zero impact, but, for reasons I have yet to understand, no_proxy="*"
does. To clarify/reiterate, this command does not work:
OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES ansible-playbook -i inventories/testing.aws_ec2.yml playbook.yml --tags config
but this command does:
no_proxy="*" ansible-playbook -i inventories/testing.aws_ec2.yml playbook.yml --tags config
@fishfacemcgee Thank you for reporting this. I guess there's a known issue with Python app forking on macOS. Please have a look here https://github.com/python/cpython/issues/74570#issuecomment-1093748531 for a detailed explanation. Since the error is not originating from the collection, I'm closing the issue, but feel free to reopen if something is unclear.
@alinabuzachis I understand that this is an issue with CPython and MacOS, but are you also saying that the Ansible AWS Collection does not/has not/will not implement mitigations for lower level platform issues in its modules or even document the compatibility issue?
Going by the comment you linked, it doesn't appear that the CPython developers are willing/able to do anything at its level to fix this either, instead recommending to use the no_proxy
environment variable. If it's a policy for this Collection to not implement any sort of platform-targeting compatibility fixes, it seems like it'd at least be worthwhile to have the issue documented.
In any case, thank you for the clarification/information.
Summary
This issue, as best I can tell is similar if not identical to #907 and #1171. However, in #907, as I best I can tell, the repo collaborator who was investigating the issue missed that the reporter had the MacOS fork flag enabled and was still running into the issue. In #1171, the issue reporter was able to resolve the issue by recreating their virtual environment. That has not worked for me.
Issue Type
Bug Report
Component Name
lookup/aws_secret.py
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
Control Node
MacOS 12.6.2 Python 3.9.13 (running via venv)
Managed Node
Amazon Linux 2
Steps to Reproduce
Expected Results
I expected the task to succeed, with the fact set with the results of the lookup.
Actual Results
Code of Conduct