"Specifying include variables at the top-level of the task is deprecated" with Ansible >= 2.0.2.0

Bug #1587661 reported by Christian Berendt on 2016-05-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Medium
Unassigned

Bug Description

PLAY [ceph-mon,ceph-osd,ceph-rgw] **********************************************

TASK [setup] *******************************************************************
ok: [de-1-node-1]
ok: [de-1-node-3]
ok: [de-1-node-2]

TASK [common : include] ********************************************************
[DEPRECATION WARNING]: Specifying include variables at the top-level of the task is deprecated. Please see:
http://docs.ansible.com/ansible/playbooks_roles.html#task-include-files-and-encouraging-reuse

 for currently supported syntax
regarding included files and variables.
This feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
included: /usr/local/share/kolla/ansible/roles/common/tasks/reconfigure.yml for de-1-node-1, de-1-node-2, de-1-node-3

Changed in kolla:
importance: Undecided → Wishlist
tags: added: low-hanging-fruit
Changed in kolla:
status: New → Triaged
Sajauddin (sajauddin-mohammad) wrote :

I thing we don't have any usage of include variables at the top-level of the task in Kolla-Ansible code.
Do we still need to anything for this?

Changed in kolla:
assignee: nobody → Surya Prakash Singh (confisurya)
Duong Ha-Quang (duonghq) wrote :

Ansible warning is not always exactly, sometime its cause is from other syntax/logic error.

Changed in kolla:
importance: Wishlist → Medium
milestone: none → ocata-1
Changed in kolla:
status: Triaged → In Progress
Changed in kolla:
milestone: ocata-1 → ocata-2
Changed in kolla:
milestone: ocata-2 → ocata-3
Christian Berendt (berendt) wrote :

Removing assignee and changing to invalid. I cannot find this deprecation warnings in the logs of a recent build on the CI.

Changed in kolla:
assignee: Surya Prakash Singh (confisurya) → nobody
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers