I'll dig into it a bit more and try to figure out why the context thread local stuff isn't cutting it - I may be able to point someone in the right direction - but I was really hoping a nova dev with some experience would be able to pitch in cause this bug is real pain.
Theirry, Thanks for reminding me that this is still an issue:
2012-03-15 14:09:12 DEBUG nova.rpc.amqp [-] received {u'_context_roles': [u'admin'], u'_context_ request_ id': u'req-c4d4f382- 5a8d-4be9- b633-21c2098197 3a', u'_context_ read_deleted' : u'no', u'args': {u'snapshot_id': None, u'volume_id': 1}, u'_context_ auth_token' : None, u'_context_ is_admin' : True, u'_context_ project_ id': u'dev1', u'_context_ timestamp' : u'2012- 03-15T19: 09:12.667410' , u'_context_ user_id' : u'admin', u'method': u'create_volume', u'_context_ remote_ address' : u'127.0.0.1'} from (pid=3947) _safe_log /opt/nova/ nova/rpc/ common. py:144 5a8d-4be9- b633-21c2098197 3a admin dev1] unpacked context: {'request_id': u'req-c4d4f382- 5a8d-4be9- b633-21c2098197 3a', 'user_id': u'admin', 'roles': [u'admin'], 'timestamp': '2012-03- 15T19:09: 12.667410' , 'is_admin': True, 'auth_token': None, 'project_id': u'dev1', 'remote_address': u'127.0.0.1', 'read_deleted': u'no'} from (pid=3947) unpack_context /opt/nova/ nova/rpc/ amqp.py: 188 nova/volume/ manager. py:120 nova/volume/ manager. py:131 nova/volume/ manager. py:145
2012-03-15 14:09:12 DEBUG nova.rpc.amqp [req-c4d4f382-
2012-03-15 14:09:12 INFO nova.volume.manager [-] volume volume-00000001: creating
2012-03-15 14:09:12 DEBUG nova.volume.manager [-] volume volume-00000001: creating lv of size 1G from (pid=3947) create_volume /opt/nova/
2012-03-15 14:09:13 DEBUG nova.volume.manager [-] volume volume-00000001: creating export from (pid=3947) create_volume /opt/nova/
2012-03-15 14:09:13 DEBUG nova.volume.manager [-] volume volume-00000001: created successfully from (pid=3947) create_volume /opt/nova/
I'll dig into it a bit more and try to figure out why the context thread local stuff isn't cutting it - I may be able to point someone in the right direction - but I was really hoping a nova dev with some experience would be able to pitch in cause this bug is real pain.