old run-upgrade script should be left in place
Bug #1506788 reported by
Darren Birkett
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Invalid
|
Undecided
|
Unassigned | ||
Kilo |
Fix Released
|
High
|
Darren Birkett | ||
Trunk |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The original run-upgrade script in kilo was being used, and is what was tested, in our environments. The new rewritten script may be better, but IMHO we should leave the old one in place, and rename the new one to run-upgrade-new.
This gives deployers the option of still using the original script, on which they may have based their upgrade tooling, but also the option of moving to the new script in the future once they are able to complete testing with that too.
To post a comment you must log in.
Fix proposed to branch: kilo /review. openstack. org/235804
Review: https:/