[octane] nova db sync broken from Juno to Liberty
Bug #1573653 reported by
Roman Sokolkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sergey Abramov | ||
8.0.x |
Won't Fix
|
High
|
Andrey Volkov | ||
Mitaka |
Fix Committed
|
High
|
Ilya Kharin | ||
Newton |
Fix Committed
|
High
|
Sergey Abramov |
Bug Description
Affected versions: 8.0+
Nova bug: https:/
nova-manage db sync fails if trying to migrate from Juno to Liberty
Workaround:
"1) Download https:/
"2) Put to upgraded controller into /tmp/2015.
"3) Execute 'tar xf /tmp/2015.
"4) Execute 'PYTHONPATH=
"5) Execute 'PYTHONPATH=
"6) Execute 'rm -rf /tmp/nova-2015.1.3 /tmp/2015.
tags: | added: area-python |
To post a comment you must log in.
Roman, only N->(N+1) upgrades are supported - you can't skip Kilo: you should do Juno->Kilo, then Kilo->Liberty upgrade instead.
Based on the discussion in https:/ /bugs.launchpad .net/nova/ +bug/1511466 my understanding is that the reporter forgot to force data migration of remaining instances (db sync only migrates DB schema and does not touch DB rows for availability sake).