Upgrade N->O nova-manage cell_v2 issue

[Grelaud]

Upgrade Newton 14.1.1 to Ocata 15.1.0

After upgrade, in horizon / Instances, click on an instance to have details on it give us this error message: "Unable to retrieve details for instance".

According to https://docs.openstack.org/developer/nova/cells.html#step-by-step-for-common-use-cases, Upgrade (minimal), in case of an existing nova database install and compute hosts in this database, after create a cell0 database, we have to run:

For exemple, in nova-api-os-compute container:
# /openstack/venvs/nova-15.1.0/bin/nova-manage cell_v2 simple_cell_setup

comment from irc by andymccr: the issue is essentially, on a new deploy nova-manage api_db sync needs to happen, but on an upgrade that cant happen until the cells are setup

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/466717

[Andy McCrae (andrew-mccrae)]

Sorry it took so long for the fix Fabrice, but the fix I put in should work moving forward!

Essentially, the step that was missing was to run a "nova-manage cell_v2 map_instances" which will take existing instances and map them to a cell, after the compute hosts are discovered. I've done a test before the patch and found the same issue as you, and after the fix ran the same test - which worked.

I hope that solves it for you, if not let us know! It needs a backport to stable/ocata still, and a SHA bump in the openstack-ansible repository for that role, but it should be good to go once that's all done.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/466717
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=4ccf26f9311830f565ce0ea2fad836ac7b3c4ff0
Submitter: Jenkins
Branch: master

commit 4ccf26f9311830f565ce0ea2fad836ac7b3c4ff0
Author: Andy McCrae <email address hidden>
Date: Mon May 22 13:27:43 2017 +0100

    Fix upgrades to map existing nova instances to cell1

    When upgrading with existing instances we need to ensure that existing
    instances are mapped into cell1.

    Change-Id: I751ea370819379687b04f06e71afa68579bcbc69
    Closes-Bug: #1682169

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/466869

[Grelaud (fabrice-grelaud)]

Thanks Andy. Happy to know, the issue was fixed for future customer upgrade.

I can't test it because my two environments are ocata already. ;-)
But i appreciate your explanation for my understanding about nova cell.

OSA is awesome !

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/466869
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=5223270ede7cd4d9e0aa7ab851acab2a6e369f7e
Submitter: Jenkins
Branch: stable/ocata

commit 5223270ede7cd4d9e0aa7ab851acab2a6e369f7e
Author: Andy McCrae <email address hidden>
Date: Mon May 22 13:27:43 2017 +0100

    Fix upgrades to map existing nova instances to cell1

    When upgrading with existing instances we need to ensure that existing
    instances are mapped into cell1.

    Change-Id: I751ea370819379687b04f06e71afa68579bcbc69
    Closes-Bug: #1682169
    (cherry picked from commit 4ccf26f9311830f565ce0ea2fad836ac7b3c4ff0)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_nova 15.1.4 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/openstack-ansible-os_nova 16.0.0.0b2 development milestone.