instances not get remapped after upgrade from newton to ocata

Bug #1677168 reported by Fairbanks.
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Fix Released
High
Unassigned

Bug Description

Hello,

After an upgrade from newton to ocata using juju run-action openstack-upgrade the instance details were not accessible any more.

Using the openstack cli i could do `openstack server list` and the servers are shown.
Executing `openstack server show <uuid>` resulted in:
"No server with a name or ID of 'uuid' exists."

This was fixed by executing the following on the nova-cloud-controller unit:
`sudo nova-manage cell_v2 list_cells`
`sudo nova-manage cell_v2 map_instances --cell_uuid <uuid for cell1>`

This should be something trigger after an upgrade procedure i think.

Revision history for this message
James Page (james-page) wrote :

This was resolved under commit 0161dde79660a248742e41e67f92ed13af561dd7 on the nova-cloud-controller charm for the 17.08 release.

Changed in charm-nova-cloud-controller:
status: New → Fix Released
importance: Undecided → High
milestone: none → 17.08
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.