openstack overcloud update stack should be powered by a mistral workflow
Bug #1614928 reported by
Dougal Matthews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Brad P. Crochet |
Bug Description
Currently the command `openstack overcloud update stack` has it's logic shared between python-
Changed in tripleo: | |
status: | Confirmed → Triaged |
Changed in tripleo: | |
assignee: | nobody → Brad P. Crochet (brad-9) |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | newton-rc2 → ocata-1 |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-1 → newton-rc3 |
tags: | removed: newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-1 → ocata-2 |
tags: | added: workflows |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
To post a comment you must log in.
As it currently stands, there is no good way to do a minor update if you have updated via the GUI. You would need to manually download the plan swift and the mistral environment and pass that information into `openstack overcloud update`