Comment 1 for bug 1306029

I do see this db lock error in the engine log:

http://logs.openstack.org/47/86047/1/check/check-tempest-dsvm-postgres-full/0f04e55/logs/screen-h-eng.txt.gz?level=TRACE#_2014-04-08_21_33_07_587

WARNING heat.engine.stack_lock [-] Lock was already released on stack 58ce15a1-f0d3-4ffe-b322-ffd714002542!

OperationalError: (OperationalError) unknown error 'SELECT resource.created_at AS resource_created_at, resource.id AS resource_id, resource.action AS resource_action, resource.status AS resource_status, resource.name AS resource_name, resource.nova_instance AS resource_nova_instance, resource.status_reason AS resource_status_reason, resource.rsrc_metadata AS resource_rsrc_metadata, resource.stack_id AS resource_stack_id, resource.updated_at AS resource_updated_at \nFROM resource \nWHERE %(param_1)s = resource.stack_id' {'param_1': u'58ce15a1-f0d3-4ffe-b322-ffd714002542'}

There are 46 hits in 7 days on that, but it's showing up in a lot of success runs too:

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiTG9jayB3YXMgYWxyZWFkeSByZWxlYXNlZCBvbiBzdGFja1wiIEFORCB0YWdzOnNjcmVlbi1oLWVuZy50eHQiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTcxNDQ4NzYzNzR9