yahoo-eng-team team mailing list archive

[Matthew Booth <mbooth@xxxxxxxxxx>]

Public bug reported:

The DatabaseAtVersion fixture starts the global TransactionContext, but
doesn't set the guard to configure() used by the Database fixture.
Consequently, if Database runs after DatabaseAtVersion in the same
worker, the subsequent fixture will fail. An example ordering which
fails is:

nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCellsCheck.test_upgrade_without_cell0
nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCheck.test_pci_device_type_vf_not_migrated

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1804811

Title:
  DatabaseAtVersion fixture causes order-related failures in tests using
  Database fixture

Status in OpenStack Compute (nova):
  New

Bug description:
  The DatabaseAtVersion fixture starts the global TransactionContext,
  but doesn't set the guard to configure() used by the Database fixture.
  Consequently, if Database runs after DatabaseAtVersion in the same
  worker, the subsequent fixture will fail. An example ordering which
  fails is:

  nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCellsCheck.test_upgrade_without_cell0
  nova.tests.unit.db.test_sqlalchemy_migration.TestNewtonCheck.test_pci_device_type_vf_not_migrated

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