Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warnings #78

Closed
hexylena opened this issue Jul 4, 2019 · 2 comments
Closed

Warnings #78

hexylena opened this issue Jul 4, 2019 · 2 comments

Comments

@hexylena
Copy link
Member

hexylena commented Jul 4, 2019

bare variable

[DEPRECATION WARNING]: evaluating galaxy_manage_static_setup as a bare variable, this behaviour will go away and you might need to add |bool to the expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle.. This
feature will be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

for the following vars:

  • galaxy_manage_static_setup
  • galaxy_create_privsep_user
  • galaxy_create_user
  • galaxy_fetch_dependencies
  • galaxy_manage_download
  • galaxy_manage_paths
  • galaxy_manage_clone
  • galaxy_manage_database (Include database management tasks)

jinja

 [WARNING]: conditional statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ galaxy_create_user if __galaxy_privsep_user_name != 'root' else false }}

more for dagobah but

[DEPRECATION WARNING]: Distribution Ubuntu 18.04 on host 192.52.34.236 should use /usr/bin/python3, but is using /usr/bin/python for backward compatibility with prior Ansible releases. A future Ansible release will default to using the
discovered platform python for this host. See https://docs.ansible.com/ansible/2.8/reference_appendices/interpreter_discovery.html for more information. This feature will be removed in version 2.12. Deprecation warnings can be disabled by
 setting deprecation_warnings=False in ansible.cfg.
@natefoo
Copy link
Member

natefoo commented Sep 25, 2019

How did you get these warnings? Even with the latest Ansible (2.8.5) I'm not seeing them.

@hexylena
Copy link
Member Author

they seem to be gone now? and we're on ansible 2.8.2 which isn't terribly outdated. Unsure!

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

No branches or pull requests

2 participants