Which was the first test after that traceback. I'm not sure what the 'no such table' is about, maybe the test is tearing down the DB before the actual service code is done running?
It also doesn't help that we're logging all of the os-traits contents at INFO each time:
b"2019-02-13 13:33:37,217 INFO [placement.objects.resource_provider] Synced traits from os_traits into API DB: {'HW_GPU_RESOLUTION_W7680H4320', 'HW_CPU_X86_SGX', 'HW_GPU_MAX_DISPLAY_HEADS_2', 'COMPUTE_VOLUME_ATTACH', 'HW_GPU_RESOLUTION_W800H600', 'HW_NIC_ACCEL_RSA', 'HW_CPU_X86_BMI', '
Another giant traceback in functional test logs:
http:// logs.openstack. org/47/ 635147/ 11/check/ nova-tox- functional- py35/5c3c2a9/ job-output. txt.gz# _2019-02- 13_13_33_ 41_103932
That dumps a ton of traceback from:
b'oslo_ db.exception. DBNonExistentTa ble: (sqlite3. OperationalErro r) no such table: instances
Since there is some sort of reschedule happening in that test, I'm assuming it's coming from:
{2} nova.tests. functional. regressions. test_bug_ 1784353. TestRescheduleW ithVolumesAttac hed.test_ reschedule_ with_volume_ attached [] ... inprogress
Which was the first test after that traceback. I'm not sure what the 'no such table' is about, maybe the test is tearing down the DB before the actual service code is done running?
It also doesn't help that we're logging all of the os-traits contents at INFO each time:
b"2019-02-13 13:33:37,217 INFO [placement. objects. resource_ provider] Synced traits from os_traits into API DB: {'HW_GPU_ RESOLUTION_ W7680H4320' , 'HW_CPU_X86_SGX', 'HW_GPU_ MAX_DISPLAY_ HEADS_2' , 'COMPUTE_ VOLUME_ ATTACH' , 'HW_GPU_ RESOLUTION_ W800H600' , 'HW_NIC_ACCEL_RSA', 'HW_CPU_X86_BMI', '