yahoo-eng-team team mailing list archive

[Ben Nemec <openstack@xxxxxxxxxxxx>]

I would prefer not to have to apply the workaround to all of the Olso
projects when we need to migrate them to stestr anyway.

** Changed in: oslo.versionedobjects
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1229445

Title:
  db type could not be determined

Status in Ironic:
  Fix Released
Status in Magnum:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.versionedobjects:
  Won't Fix
Status in Python client library for Sahara:
  Invalid
Status in tempest:
  Incomplete
Status in Testrepository:
  Triaged
Status in Zun:
  Fix Released

Bug description:
  In openstack/python-novaclient project, run test in py27 env, then run
  test in py33 env,  the following error will stop test:

  db type could not be determined

  But, if you run "tox -e py33" fist, then run "tox -e py27", it will be
  fine, no error.

  workaround:
  remove the file in .testrepository/times.dbm, then run py33 test, it will be fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1229445/+subscriptions