[DEPRECATION WARNING]: Skipping task due to undefined attribute

[khromov]

Getting these errors on first-run vagrant up . Is this anything to worry about and does it break the deploy?

==> default: TASK [php : Install Package] ***************************************************
==> default: [DEPRECATION WARNING]: Skipping task due to undefined attribute, in the future
==> default: this will be a fatal error.. This feature will be removed in a future release.
==> default: Deprecation warnings can be disabled by setting deprecation_warnings=False in
==> default: ansible.cfg.
==> default:
==> default: TASK [php : Create extension .ini file] ****************************************
==> default: [DEPRECATION WARNING]: Skipping task due to undefined attribute, in the future
==> default: this will be a fatal error.. This feature will be removed in a future release.
==> default: Deprecation warnings can be disabled by setting deprecation_warnings=False in
==> default: ansible.cfg.
==> default:
==> default: TASK [php : Enable extension] **************************************************
==> default: [DEPRECATION WARNING]: Skipping task due to undefined attribute, in the future
==> default: this will be a fatal error.. This feature will be removed in a future release.
==> default: Deprecation warnings can be disabled by setting deprecation_warnings=False in
==> default: ansible.cfg.

[naxhh]

Hi! It shouldn't break your deploy since it's a Warning and not a fatal error.
@khromov just to know, which version of ansible are you using?

But this require us to update the php module to not get the deprecation warning.
For people interested in contributing:

Seems this is related to php role in the pecl section.
https://github.com/phansible/role-php/blob/5e48f73189c10f16644f0120899bc94978579ffa/tasks/pecl.yml#L5

It should be as easy as checking the new documentation and adding the required params

[khromov]

@naxhh It's a 14.04 deployed on Windows, so it uses windows.sh. The version you get from the apt-get command is 2.0.0.2 currently.

[naxhh]

ansible client version :p

ansible --version

[khromov]

Should be right!

vagrant ssh
...
vagrant@vagrant-ubuntu-trusty-64:~$ ansible --version
ansible 2.0.0.2
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides

[naxhh]

Ok thanks! So the warnings are due to 2.0 version. We will be cleaning this warnings, thanks for reporting

[debo]

Hey guys, sorry for the delay guys, I had a busy weekend, I'll start following up with the pending issues tonight. And yes it's more a warning about what to expect in future from ansible 2.0 which means we need to update the role accordingly as required moving forward.