--templates option on `overcloud update stack` is unused
Bug #1745988 reported by
Jiří Stránský
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Medium
|
Jiří Stránský |
Bug Description
Passing --templates option into `overcloud update stack` has no effect, it is not referenced in the update code.
If we implement it, we probably need to redo the deployment plan during update init (similarly as if we'd run `overcloud deploy`), and we'd have to implement all the parameters from `overcloud deploy` too. We might want to just remove the --templates option instead, as the current `overcloud update stack` command operates just by slightly altering the existing deployment plan. Further investigation might be in order to tell whether this is sufficient or not.
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: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
Changed in tripleo: | |
milestone: | stein-3 → train-1 |
Changed in tripleo: | |
milestone: | train-1 → train-2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/539261
Review: https:/