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

[lots of] deprecation warnings in Ansible 2.8 #221

Closed
sfuerte opened this issue May 28, 2019 · 4 comments
Closed

[lots of] deprecation warnings in Ansible 2.8 #221

sfuerte opened this issue May 28, 2019 · 4 comments

Comments

@sfuerte
Copy link

sfuerte commented May 28, 2019

Describe the bug

DEPRECATION WARNING]: evaluating os_hardening_enabled 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.

[DEPRECATION WARNING]: Use errors="ignore" instead of skip. This feature will be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

[DEPRECATION WARNING]: evaluating os_hardening_enabled 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.

[DEPRECATION WARNING]: evaluating os_security_kernel_enable_core_dump 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.

Expected behavior
Clean run with no warnings

Example Playbook

...
  roles:
    - role: dev-sec.os-hardening
...

OS / Environment
Ansible Version

# ansible --version
ansible 2.8.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Mar 26 2019, 22:13:06) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

Role Version

# ansible-galaxy list  | grep os-hard
- dev-sec.os-hardening, 5.2.0
@rndmh3ro
Copy link
Member

rndmh3ro commented Jun 2, 2019

Thanks @sfuerte for opening this issue.

As this seems easy to fix, I added the help-wanted label so anyone who wants to can create a PR!

@Normo
Copy link
Contributor

Normo commented Jun 6, 2019

@rndmh3ro,
#224 fixes allmost all deprecation warnings except for:
[DEPRECATION WARNING]: Use errors="ignore" instead of skip. This feature will be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

@rndmh3ro
Copy link
Member

rndmh3ro commented Jun 8, 2019

It seems the last deprecation warning won't go away until Ansible 2.9 so lets wait for it and keep the ticket open.

@rndmh3ro rndmh3ro added this to Up for grabs in Hacktoberfest 2019 Oct 2, 2019
@rndmh3ro rndmh3ro removed this from Up for grabs in Hacktoberfest 2019 Oct 4, 2019
@rndmh3ro
Copy link
Member

Ansible 2.9 is released and I see no more deprecation warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants