Skip to content

Conversation

eb4x
Copy link

@eb4x eb4x commented Jun 15, 2021

This is probably the result of a bigger underlying problem, but
setting deprecation_warnings = False fixed the warning below

TASK [scaffold_rm_facts : Create the file, if it doesnt exist already or override is set] ****************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: """
fatal: [localhost]: FAILED! => {
"changed": false
}

MSG:

AnsibleError: Failed to validate the model with error: Error while parsing module: b'[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the \ncontroller starting with Ansible 2.12. Current version: 3.6.8 (default, Mar 18 \n2021, 08:58:41) [GCC 8.4.1 20200928 (Red Hat 8.4.1-1)]. This feature will be \nremoved from ansible-core in version 2.12. Deprecation warnings can be disabled\n by setting deprecation_warnings=False in ansible.cfg.\n'

This is probably the result of a bigger underlying problem, but
setting deprecation_warnings = False fixed the warning below

TASK [scaffold_rm_facts : Create the file, if it doesnt exist already or override is set] ****************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: """
fatal: [localhost]: FAILED! => {
    "changed": false
}

MSG:

AnsibleError: Failed to validate the model with error: Error while parsing module: b'[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the \ncontroller starting with Ansible 2.12. Current version: 3.6.8 (default, Mar 18 \n2021, 08:58:41) [GCC 8.4.1 20200928 (Red Hat 8.4.1-1)]. This feature will be \nremoved from ansible-core in version 2.12. Deprecation warnings can be disabled\n by setting deprecation_warnings=False in ansible.cfg.\n'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant