# Issue with Ansible on Rocky Linux 8.10 (Python 3.12) – "future feature annotations is not defined" **URL:** \ **Category:** Get Help\ **Tags:** centos, rockylinux\ **Created:** [March 19, 2025, 8:09am UTC](https://forum.ansible.com/t/issue-with-ansible-on-rocky-linux-8-10-python-3-12-future-feature-annotations-is-not-defined/41117 "2025-03-19T08:09:31Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [March 19, 2025, 2:29pm UTC](https://forum.ansible.com/t/issue-with-ansible-on-rocky-linux-8-10-python-3-12-future-feature-annotations-is-not-defined/41117/2 "2025-03-19T14:29:50Z")
ansible-core 2.17 and newer do not support the default system python 3.6. I know you mention python3.12, however the `dnf` module requires the python dnf/rpm/gpgme/etc bindings, which are only packaged for the system python. We have a feature called “respawn” which will attempt to respawn the module being executed, against known system python versions if the python bindings are missing from the python version specified by `ansible_python_interpreter`. As such, in order for the `dnf` module to potentially work, it has to respawn on an interpreter that supports the python bindings it requires. We’ve recently improved the method in which the other python interpreters are polled for respawn, to omit python versions that we no longer support. But that only cleans up the messaging on the failure to run the module. So long story short, ansible-core 2.17+ simply cannot perform package related tasks against RHEL8. There are other modules in other collections that also won’t work as well due to this limitation. --- _[View the full topic](https://forum.ansible.com/t/issue-with-ansible-on-rocky-linux-8-10-python-3-12-future-feature-annotations-is-not-defined/41117)._