[Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp

[Christian Ehrhardt ]

Hrm, this is not my homest of home turfs :-/
- tox based test calling (as mentioned upstream) blocks on pip install
- the python3-stestr based test fails to find resources when stripped

This works:
$ pkgos-dh_auto_test --no-py2 "cinder.tests.unit.api.contrib.test_volume_type_encryption.VolumeTypeEncryptionTest.test_create_volume_exists" 2>&1 | tee testlog-3.26.0-2.summary

Looking back I realized you seem to have adapted your Debian rules to
call it rather similarly.

This works (and has a bit more unreadable debug data than the other
call):

$PYTHON=python3.7 python3-stestr run --subunit
"cinder.tests.unit.api.contrib.test_volume_type_encryption.VolumeTypeEncryptionTest.test_create_volume_exists"
2>&1 | tee testlog-3.26.0-2.details

Only in the good case I see this:
/usr/lib/python3/dist-packages/sqlalchemy/orm/evaluator.py:71: SAWarning: Evaluating non-mapped column expression 'updated_at' onto ORM instances; this is a deprecated use
    "UPDATE / DELETE expressions." % clause)

Maybe sqlite finally dropped this, but I'm not sure as this is a
deprecation warning of python3-sqlalchemy and not sqlite3.

I then modified the test to fail in any case, that will spill more debug
in the good case (if the test is good then it will only say ok).

That let me compare the info and warnings in the beginning between good/bad case:
The four INFO/WARNING on keystonemiddleware.auth_token, keystonemiddleware._common.config, keystonemiddleware.auth_token are the same in good and bad case.

The next entry in good case that is missing in the bad case is:
2018-12-07 09:13:42,744 INFO [cinder.rpc] Automatically selected cinder-scheduler objects version 1.37 as minimum service version.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1807262

Title:
  stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
  migration_tmp

Status in cinder package in Ubuntu:
  Triaged
Status in nova package in Ubuntu:
  Triaged
Status in sqlite3 package in Ubuntu:
  New

Bug description:
  Several tests that use sqlite fail with:
  "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
  hitting this with nova and cinder packages in disco.

  Note this started sometime after 11/19 when nova
  2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
  successfully at the time).

  After doing some digging this appears to occur with libsqlite3-0
  3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
  more details on that, shown by running a failing unit test from the
  cinder package: https://paste.ubuntu.com/p/hsnQFQD572/

  Update: The test in the paste above also works successfully with
  libsqlite3-0 3.25.3-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions