Deploy steps executed twice during `update run`
Bug #1776206 reported by
Jiří Stránský
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiří Stránský |
Bug Description
It seems that we run deployment tasks twice during minor update. From observation, the likely order is:
1) update_tasks
2) deploy tasks (puppet, containers)
3) host_prep_tasks
4) deploy tasks again
Points 1 and 2 get executed in `serial: 1` manner (as they should). After that normal deployment playbook runs in parallel on all nodes -- that part seems superfluous, as `update converge` would do a very similar thing.
summary: |
- Deploy steps executed twice during minor version update + Deploy steps executed twice during `update run` |
tags: | added: queens-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/574230
Review: https:/