When this test is run, the DB API throws the following error. This does not look benign.
DBAPIError exception wrapped from (sqlite3.InterfaceError) Error binding parameter 0 - probably unsupported type. \
[SQL: u'SELECT instances.id AS instances_id, instances.created AS instances_created, instances.updated AS instance\
s_updated, instances.name AS instances_name, instances.hostname AS instances_hostname, instances.compute_instance_\
id AS instances_compute_instance_id, instances.task_id AS instances_task_id, instances.task_description AS instanc\
es_task_description, instances.task_start_time AS instances_task_start_time, instances.volume_id AS instances_volu\
me_id, instances.flavor_id AS instances_flavor_id, instances.volume_size AS instances_volume_size, instances.tenan\
t_id AS instances_tenant_id, instances.server_status AS instances_server_status, instances.deleted AS instances_de\
leted, instances.deleted_at AS instances_deleted_at, instances.datastore_version_id AS instances_datastore_version\
_id, instances.configuration_id AS instances_configuration_id, instances.slave_of_id AS instances_slave_of_id, ins\
tances.cluster_id AS instances_cluster_id, instances.shard_id AS instances_shard_id, instances.type AS instances_t\
ype \nFROM instances \nWHERE instances.id = ? AND instances.deleted = 0\n LIMIT ? OFFSET ?'] [parameters: (<Mock i\
d='140681201083344'>, 1, 0)]
Traceback (most recent call last):
File "/opt/upstream/trove/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1139, in \
_execute_context
context)
File "/opt/upstream/trove/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 450, i\
n do_execute
cursor.execute(statement, parameters)
InterfaceError: Error binding parameter 0 - probably unsupported type.
*************************
Unhandled message logged from taskmanager.test_pxc_clusters.PXCClusterTasksTest.test_shrink_cluster_does_not_exist\
, oslo_db.sqlalchemy.exc_filters
This error is the effect of not mocking out the database call and the exception is printed out but the test passes as expected. There is no bad side effects other than the exception being printed out here. I'll patch this db call.