You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If there is Python 2 & 3 at the same time, ansible-core 2.11 will choose Python 2 by default. Due to Ubuntu release upgrade we've changed setting interpreter_python from auto_legacy_silent to auto in ansible.cfg. However, this config file may by not applied when running playbooks manually (for developing) unless ANSIBLE_CONFIG is set. ansible-core 2.12 solves this issue since it uses different default value for interpreter_python (auto).
Describe the solution you'd like
Ansible in latest version.
Describe alternatives you've considered
n/a
Additional context
n/a
DoD checklist
Changelog updated
COMPONENTS.md updated / doesn't need to be updated
Schema updated / doesn't need to be updated
Feature has automated tests
Automated tests passed (QA pipelines)
apply
upgrade
Idempotency tested
Documentation added / updated / doesn't need to be updated
All conversations in PR resolved
Solution meets requirements and is done according to design doc
Usage compliant with license
Backport tasks created / doesn't need to be backported
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If there is Python 2 & 3 at the same time, ansible-core 2.11 will choose Python 2 by default. Due to Ubuntu release upgrade we've changed setting
interpreter_python
fromauto_legacy_silent
toauto
in ansible.cfg. However, this config file may by not applied when running playbooks manually (for developing) unlessANSIBLE_CONFIG
is set. ansible-core 2.12 solves this issue since it uses different default value forinterpreter_python
(auto
).Describe the solution you'd like
Ansible in latest version.
Describe alternatives you've considered
n/a
Additional context
n/a
DoD checklist
The text was updated successfully, but these errors were encountered: