There is a retry logic in httplib2 used by neutron that automatically retries requests. One instance when this kicks in is: client makes a connection —> issues request to the server —> server takes too long to respond (if busy) —> client socket timesout waiting for response and client goes for a retry. The end result is that the request may get processed twice at the server. There is a parameter RETRIES used in _conn_request(…) defined in __init__.py. This parameter is not configurable, hard-coded to 2.
One possible way to deal with this is to increase the timeout value (which is configurable) to a larger value. The default is 30 seconds and increasing it to larger value helps. This will not solve the issue, but could make it less likely to occur. Here are Google references to the retry logic in httplib2: https://code.google.com/p/httplib2/issues/detail?id=109 https://groups.google.com/forum/#!msg/google-api-python-client/VE1d7a7Wevg/elmt1MDsjmAJ http://httplib2.googlecode.com/hg/doc/html/libhttplib2.html ** Bug watch added: code.google.com/p/httplib2/issues #109 http://code.google.com/p/httplib2/issues/detail?id=109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160442 Title: when boot many vms with quantum, nova sometimes allocates two quantum ports rather than one To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1160442/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
