What were you trying to do that didn't work?

Ansible collecting remote local_facts doesn't work anymore if target machine is using python 3.12, which is the case for RHEL10, so wouldn't return correct variables when the ansible management host is running on RHEL9

What is the impact of this issue to you?

Incorrect collected variables meaning incorrect ansible orchestration/play/role due to undefined variables and boolean

Please provide the package NVR for which the bug is seen:

ansible-core-2.14.17-1.el9.x86_64

How reproducible is this bug?:

Always, and known upstream (https://github.com/ansible/ansible/issues/84824)

Steps to reproduce

1. create .fact file under /etc/ansible/facts.d in ini format (still documented as working : https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_vars_facts.html#facts-d-or-local-facts
2. collect info from a stream10/rhel10 host and see nothing being returned
3.  

Expected results

ansible c10s-test.dev.centos.org -m ansible.builtin.setup -a "filter=ansible_local" -b
c10s-test.dev.centos.org | SUCCESS => {
"ansible_facts": {
"ansible_local": {
"hba": {
"adapters":

{ "3w_9xxx": "False", "3w_xxxx": "False", "aacraid": "False", "arcmsr": "False", "megaraid_sas": "False", "mpi3mr": "False" }

}
}
},
"changed": false
}
 

Actual results

ansible c10s-test.dev.centos.org -m ansible.builtin.setup -a "filter=ansible_local" -b
c10s-test.dev.centos.org | SUCCESS => {
"ansible_facts": {},
"changed": false
}
 

Worth knowing that upstream bug has also link to .patch that can be backported (tested locally)