[RFE] improve `openstack undercloud upgrade' rollback capabilities
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
Dear Stackers,
The following command should do a dump of all mysql database prior anything: `openstack undercloud upgrade'
This would allow anyone to do a clean rollback of an upgrade.
In addition, it would be great if that same command could in some way do a backup of the /usr/share/
Small idea with the latter: in our env, we actually copied the whole directory somewhere else in order to manage its content with git, outside of yum managed contents.
We hence have a small update script that do all what's needed for us:
http://
This means, once the upgrade is over, we just have to do a "git commit --all" in the local template directory.
This, in addition to the mysql dump, would allow a clean rollback, even if the stack is broken (like we had just today).
Care to check that feature request? :).
Thank you!
Cheers,
C.
| Changed in tripleo: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| milestone: | none → queens-3 |
| tags: | added: upgrade |
| 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: | |
| 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 |
| Changed in tripleo: | |
| milestone: | train-2 → train-3 |
| Changed in tripleo: | |
| milestone: | train-3 → ussuri-1 |
| mathieu bultel (mat-bultel) wrote | #1 |
| Carlos Camacho (ccamacho) wrote | #2 |
| Changed in tripleo: | |
| status: | Triaged → Invalid |
This RFE has been solved by the Backup and restore procedure AFAIK.
I think we can close it.