tripleo triggers ansible deprecation warnings

Bug #1811778 reported by Sorin Sbarnea
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
Medium
Sorin Sbarnea

Bug Description

This is a tracing bug for all deprecation warnings triggered by Ansible in tripleo code. These warnings need to be addressed in order to be able to move forward and upgrade to the next versions of Ansible.

The purpose of the bug is to track and fix such issue but not other bugs that could prevent Ansibe upgrades, this being limited to [DEPRECATION WARNING] or similar.

Sorin Sbarnea (ssbarnea)
Changed in tripleo:
assignee: nobody → Sorin Sbarnea (ssbarnea)
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Juan Antonio Osorio Robles (juan-osorio-robles) wrote :

Is this still an issue?

Revision history for this message
Sorin Sbarnea (ssbarnea) wrote :

YES, lots of warnings and this tickets is unlikely to be addressed very soon.

Few examples of warnings found in our logs:

[WARNING]: Found both group and host with same name:
[WARNING]: Ignoring invalid attribute: executable
[DEPRECATION WARNING]: Using tests as filters is deprecated. Instead of using

We could even try to make a e-r logstash query to count them over time but I am not sure if I can convince the maintainers to accept that patch as the tools was used historically to identify failures, not warnings.

wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.