25c737d6b8
On offline upgrades, due to the rolling upgrade mechanism we need to
restart the cinder services twice to complete the upgrade, just like in
the rolling upgrade case.
The current offline upgrade process is:
- Stop cinder services
- Upgrade the cinder nodes
- Sync your DB
- Start the cinder services
- Restart all the cinder services
This second restart creates a bad user experience and it should not be
necessary on an offline upgrade, so this patch adds a new optional
parameter -called "--bump-versions"- to the cinder-manage db sync
command that allows us to skip the restart of the services.
Closes-Bug: #1756321
Change-Id: I1b58c637f6b2187a78c9c00a6c4933335439ad6f
(cherry picked from commit 3cd2ebd375)
17 lines
887 B
YAML
17 lines
887 B
YAML
---
|
|
features:
|
|
- Cinder-manage DB sync command can now bump the RPC and Objects versions of
|
|
the services to avoid a second restart when doing offline upgrades.
|
|
upgrade:
|
|
- On offline upgrades, due to the rolling upgrade mechanism we need to
|
|
restart the cinder services twice to complete the installation just like in
|
|
the rolling upgrades case. First you stop the cinder services, then you
|
|
upgrade them, you sync your DB, then you start all the cinder services, and
|
|
then you restart them all. To avoid this last restart we can now instruct
|
|
the DB sync to bump the services after the migration is completed, the
|
|
command to do this is `cinder-manage db sync --bump-versions`
|
|
fixes:
|
|
- After an offline upgrade we had to restart all Cinder services twice, now
|
|
with the `cinder-manage db sync --bump-versions` command we can avoid the
|
|
second restart.
|