OpenStack Compute (nova)

  1. Series ussuri
  2. Bug #1837995
  3. Comment #10

Comment 10 for bug 1837995

Revision history for this message
melanie witt (melwitt) wrote :

FWIW I am able to reproduce a state where the error is raised:

Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
<class 'nova.exception.OrphanedObjectError'> (HTTP 500) (Request-ID: req-75f3d4f1-9cb3-4d46-a0da-54f63764a0bb)

by using the following steps to get into a state where the database has been only partially archived:

http://paste.openstack.org/show/801782

To get an error for 'openstack usage', the deleted [but not purged] instance has to have been ACTIVE at some point in the past and to do a full archive before starting the --max_rows 1 loop to speed up hitting the bug.

If an instance's 'instance_extr'a record is archived (moved to the shadow table) while the 'instances' record remains, OrphanedObjectError will be hit for various API requests.