yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1645810@xxxxxxxxxxxxxxxxxx>]

Also we don't lock records anymore.

** Tags removed: needs-attention

** Changed in: neutron
       Status: New => Fix Released

** Changed in: neutron
       Status: Fix Released => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1645810

Title:
  neutron  api update port and agent rpc  update port timestamp  may
  cause db deadlock

Status in neutron:
  Opinion

Bug description:
  The test scenario as follow steps :

  1,server api update some attributes of port ,like hostid:
  	(1),ml2 plugin: update_port  ----> db.get_locked_port_and_binding .
  	(2),server api thread get port db update lock  , and wait for release lock to update timestamp.

  2,ovs agent receive rpc message ,handler update port statues
  	(1),ovs agent rpc method update_port_status is called 
  	(2),in this method it will flush session firstly to get  timestamp lock for updating port 

  3,at the this time :
  	(1),agent rpc get timestamp lock to update timestamp  
  	(2),server api get port lock to update port 
      (3),agent method update_port_status wait for port lock , but server method db.get_locked_port_and_binding also wait for timestamp lock which caused deadlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1645810/+subscriptions