Comment 4 for bug 735974

Hi,

Sorry, in my case on RHEL6, it turned out that my symptom was cause by a configuration error. I succeeded to launch a vm using trunk rev 912 even if we got the above error messages regarding fixed_ip_disassociate_all_by_timeout.

But, anyway it looks like that we can suppress the above error messages by suppliyng
an additional parameter 'synchronize_session' as the error message line says.

Explanation of 'synchronize_session' is available below:
  http://www.sqlalchemy.org/docs/orm/query.html?highlight=synchronize_session
and, I would suggest the fix below.

Signed-off-by: Masaori Itoh <email address hidden>

=== modified file 'nova/db/sqlalchemy/api.py'
--- nova/db/sqlalchemy/api.py 2011-03-25 14:21:03 +0000
+++ nova/db/sqlalchemy/api.py 2011-03-30 09:13:29 +0000
@@ -660,7 +660,7 @@
                      filter(models.FixedIp.instance_id != None).\
                      filter_by(allocated=0).\
                      update({'instance_id': None,
- 'leased': 0})
+ 'leased': 0}, synchronize_session='fetch')
     return result