yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1367354@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package keystone - 1:2014.2~b3-0ubuntu2

---------------
keystone (1:2014.2~b3-0ubuntu2) utopic; urgency=medium

  * Start failing package builds on unit test failures again:
    - d/rules: Fail build on any test failures.
    - d/p/skip-pysaml2.patch: Skip federation tests for now as pysaml2 is
      not yet in Ubuntu main and federation is only a contrib module.
    - d/p/bug-1371620.patch: Cherry pick fix from upstream VCS for db locking
      issues with sqlite during package install (LP: #1371620).
    - d/p/bug-1367354.patch: Cherry pick fix from upstream VCS to ensure that
      downgrade tests on sqlite complete successfully (LP: #1367354).
    - d/control: Add missing python-ldappool to BD's.
  * d/control: Align version requirements for pycadf and six with upstream.
  * d/p/series: Re-enable disabled add-version-info.patch.
 -- James Page <james.page@xxxxxxxxxx>   Mon, 29 Sep 2014 15:34:45 +0100

** Changed in: keystone (Ubuntu)
       Status: Triaged => Fix Released

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

Title:
  oslo.db's master breaks unittest in OS projects

Status in OpenStack Identity (Keystone):
  Fix Committed
Status in OpenStack Compute (Nova):
  Confirmed
Status in Oslo Database library:
  Fix Released
Status in “keystone” package in Ubuntu:
  Fix Released

Bug description:
  When I run the unittests in different OpennStack projects using the
  latest oslo.db there were a lot of failures on Nova, Neutron and
  Keystone. The lot of tests raises OperationalError: (OperationalError)
  cannot start a transaction within a transaction 'BEGIN' () The right
  approach is to fix these projects, but we are in the end of J release,
  so I'm not sure, that we can merge these fixes fast.

  This issue was caused by commit [1], so the faster and simplest
  approach is - to revert this commit an continue our fork on this in K

  [1]
  https://github.com/openstack/oslo.db/commit/78fd290a89545de31e5c13f3085df23368a8afaa

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