nova upgrade failures from newton to ocata
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Expired
|
Undecided
|
Unassigned |
Bug Description
I'm running an upgrade from kolla 3.0.3 to kolla 4.0.2, with a local registry and a build from source/centos.
I had a first failure when running the nova-manage commands from the nova_api container :
https:/
Those tasks complain that they don't have write permissions on /var/log/
I had to enter the nova_api container and change permissions on this file.
Then the "Running Nova bootstrap container" fails. Logs on the nova_bootstrap container shows the following error :
ValidationError: Cell mappings are not created, but required for Ocata. Please run nova-manage cell_v2 simple_cell_setup before continuing.
When looking at the db, it appears that the nova_api.
# nova-manage --verbose cell_v2 map_cell_and_hosts --transport-url rabbit:
It should have been run by the following task :
But in my case, the "nova_api nova-manage cell_v2 simple_
Changed in kolla-ansible: | |
status: | New → Incomplete |
I tried a couple of time to verify this issue but I was unable to reproduce.
Here is one of the upgrade process logs http:// paste.openstack .org/show/ 610147/ paste.openstack .org/show/ 610138/
And sample cell creation process http://
map_cell_and_hosts should be executed during simple_cell_setup (Newton code) https:/ /github. com/openstack/ nova/blob/ stable/ newton/ nova/cmd/ manage. py#L1248
Basically what simple_cell_setup does is:
- Create cell0 mapping (we do this manually before setup cells to point to correct database(newton pointed to nova_api_cell0 instead of nova_cell0))
- Run DB sync for cell0 db schema
- Run map_cell_and_hosts
- Map instances into a cell (None if not using cells)
My guess on this issue:
- Something goes wrong before simple_cell_setup
- Kolla code was not in ocata branch (note than newton or master does not have cell creation during upgrade)
- Tried several times the upgrade on the same environment and things get unstable
- Wrong code or images used (There was a bug in nova before 3.0.3)