Instance not mapped after running command "nova-manage cell_v2 map_instances --cell_uuid <cell_uuid>".

[Saurabh jangir]

I tried to map an instance with a cell by command 'nova-manage cell_v2 map_instances --cell_uuid <cell_uuid>' .Below are the commands and output of terminal.

[root@localhost ~(keystone_admin)]# nova-manage cell_v2 list_cells
+----------+--------------------------------------+
| Name | UUID |
+----------+--------------------------------------+
| None | 224579a3-579e-4d49-8b22-a3bd4cad9e08 |
| cell0 | 00000000-0000-0000-0000-000000000000 |
| new_cell | 5fccc557-4704-411f-9e1e-539f5052a828 |
+----------+--------------------------------------+

[root@localhost ~(keystone_admin)]# nova-manage cell_v2 map_instances --cell_uuid 5fccc557-4704-411f-9e1e-539f5052a828
[root@localhost ~(keystone_admin)]# nova-manage cell_v2 verify_instance --uuid 2dcca7d1-9ba0-4466-9d91-a9cb5ff04b55
Instance 2dcca7d1-9ba0-4466-9d91-a9cb5ff04b55 is not mapped to a cell (upgrade is incomplete)

Even after executing command to map instance with cell "new_cell", the instance is not mapped to any cell.
Code says that this is due to incomplete upgrade.

[Matt Riedemann (mriedem)]

Is this a fresh install or are you upgrading an existing non-cellsv2 deployment to cellsv2?

Have you gone through the install steps in this doc?

https://docs.openstack.org/nova/latest/user/cells.html

[Surya Seetharaman (tssurya)]

This was effecting me as well because the config file that nova-manage was using, was not pointing to the DB of newly created cell where the unmapped instances were. It was pointing to the default cell0 database.

Once I gave the config file of the newly created cell using the --config-file option map_instances worked. My bad, so I am reverting the status of this bug to its old condition.

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]