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
Describe the bug
I upgrade today my data-node to 4.0.3 using esgf-ansible, and I notice a deprecation warning in ansible logs
To Reproduce
Steps to reproduce the behavior:
Run installer with : ansible-playbook -i "${INVENTORY}" -u root --tags data --limit "${HOST_NAME}" --skip-tags gridftp install.yml
see error
2019-10-01 07:41:29,994 p=65375 u=root | [DEPRECATION WARNING]: evaluating (is_7 and firewalld_enabled is defined and firewalld_enabled is changed) 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.
ESGF Node :
Managed OS: centos 7
ansible : ansible-2.8.4-1.el7.noarch
esgf-ansible Version:4.0.3
Node type: data-only
node name : esg1.umr-cnrm.fr
The text was updated successfully, but these errors were encountered:
Describe the bug
I upgrade today my data-node to 4.0.3 using esgf-ansible, and I notice a deprecation warning in ansible logs
To Reproduce
Steps to reproduce the behavior:
2019-10-01 07:41:29,994 p=65375 u=root | [DEPRECATION WARNING]: evaluating (is_7 and firewalld_enabled is defined and firewalld_enabled is changed) 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.
ESGF Node :
The text was updated successfully, but these errors were encountered: