Why are we using legacy Ansible syntax in upgrade_tasks?

Bug #1715635 reported by Lars Kellogg-Stedman
2
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Medium
Unassigned

Bug Description

Ansible tasks in the ugprade_tasks block of our service mix modern and legacy ansible syntax. Can we just settle on the more modern syntax? That is, instead of:

            - name: Stop and disable nova_api service (pre-upgrade not under htt
              tags: step2
              service: name=openstack-nova-api state=stopped enabled=no

Can we use:

            - name: Stop and disable nova_api service (pre-upgrade not under htt
              tags: step2
              service:
                name: openstack-nova-api
                state: stopped
                enabled: no

Adopting a common syntax means that it's easier to spot errors, and the advantage of the modern syntax is that it's all just YAML so it's trivial to programatically extract information from playbooks.

Revision history for this message
Alex Schultz (alex-schultz) wrote :

Can we enforce only one syntax via a linter?

Changed in tripleo:
milestone: none → queens-1
importance: Undecided → Medium
status: New → Triaged
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
status: Triaged → Invalid
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.