Comment 12 for bug 1381536

Is there any overall information available about what this mechanism driver (named 'mech_driver') is doing?

Is it a coincidence that the DHCP agent makes an RPC call to create the DHCP port at the same time as the create_port_postcommit is failing? Or is it something like:
- mech_driver is asked to create a port
- as part of that, it sends some signal to the compute host, which causes the DHCP agent there to try to create the DHCP port
- an SSL error occurs in the communication between the mech_driver and the compute host, causing the mech_driver create_port operation to fail
- while that failure is being handled, the create_port comes in from the DHCP agent, leading to the ResourceClosedError.

Is the mech_driver passing the DB context to the compute host, and the compute host's DHCP agent using that same context when asking to create the DHCP port? (Is that even possible? I'm afraid I don't yet understand DB contexts/sessions well enough to know.)