© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Hi Anton,
This is strange. You have very good looking information on how to reproduce this bug but in my environment I still cannot do that.
I have two devstack environments, one for master, another for stable/xena. Both are single-host environments. I changed neutron worker settings (api, rpc, metadata) to the same as yours. Also the default db in devstack is mysql, not postgre.
Beyond the sleep() suggested by you I have even added another sleep(3) before this line:
https:/
In the master environment I even enabled vpnaas as it was enabled in your config.
But in none of these variations was I able to reproduce the bug.
I am running out of ideas what may be the difference between your environment and mine. A few more though:
* In a production environment you likely have neutron-server running on multiple hosts. If you turn neutron-server off on all hosts except one, can you still reproduce the bug?
* I'm no DB expert (especially not for postgre), but if you use any db replication cluster, can you still reproduce bug if you turn that off and you have a single host DB?
Just for later reference:
delete side db transaction:
https:/
segments are deleted from NETWORK PRECOMMIT_DELETE hook:
https:/
list side db transaction:
https:/
the debug log message in the original report comes from here:
https:/