Something is wrong with your upgrade as it claims that the 'services'
table disappeared.

Given it's a specific deployment concern, setting the bug as Invalid
since it doesn't like like a nova upstream project issue.

** Changed in: nova
       Status: New => Invalid

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).

  Unable to retrieve instances after openstack upgrade from newton to

Status in OpenStack Compute (nova):

Bug description:
  After openstack upgrade from newton to pike release, 
  1. Not able to list instances created before upgrade(though instances seems 
to be running).
  2. Not able spawn new instances after upgrade from newton to pike.


  1.Able to ping ang login into VMs which are created before upgrade.

  Below is the snippet when propmpted the command:

  **nova list**
  ERROR (ClientException): Unexpected API Error. Please report this at and attach the Nova API log if possible.
  <class 'oslo_db.exception.DBError'> (HTTP 500) (Request-ID: 

  **openstack server list**
  Unexpected API Error. Please report this at 
and attach the Nova API log if possible.
  <class 'oslo_db.exception.DBError'> (HTTP 500) (Request-ID: 

  Note: When tried with openstack-dashboard webui faces same issue. It
  throws an error "unable to retrieve instances".

  Steps to reproduce:
  1.Deploy openstack newton.
  2.Spawn some VMs
  3.Upgrade openstack from newton to pike
  4.list the VMs using "nova list" command 

  Expected results:
  1. Should be able to list VMs spawned before upgrade.
  2. Should able to spawn new VMs

  Obtained result:
  1. Unable to retrieve the instances
  2. Not able to spawn VMs

  Description of the environment:
  * 9 baremetal nodes:
    -1st node has MAAS Deployed.
    -MAAS will deploy OS on all other nodes
    -Using juju openstack is deployed
  *Node roles
    -3 compute node
    -3 controller node
    -2 network node
  * Details:
    - Newton on Ubuntu 14.04
    - Compute: KVM

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to