Lock wait timeout inserting row into routers table

[Eugene Nikanorov]

Another instance of the famous bug:

http://logs.openstack.org/87/99187/1/check/check-tempest-dsvm-neutron-full/978727a/logs/screen-q-svc.txt.gz?level=TRACE#_2014-06-20_03_10_37_447

OperationalError: (OperationalError) (1205, 'Lock wait timeout exceeded; try restarting transaction') 'INSERT INTO routers (tenant_id, id, name, status, admin_state_up, gw_port_id, enable_snat) VALUES (%s, %s, %s, %s, %s, %s, %s)' ('91f1077240284b0a85e9bb8a02712926', '04003809-f94c-42ef-ad5a-d84dd0b0a086', 'AttachVolumeV3Test-488061603-router', 'ACTIVE', 1, None, 1)

[Cedric Brandily (cbrandily)]

This bug is > 365 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Ihar Hrachyshka (ihar-hrachyshka)]

I believe timeouts are not reproducible with pymysql that we use in gate now.

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]