Race condition for default security group
Bug #1471287 reported by
Muawia Khan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-plumgrid |
Fix Committed
|
Critical
|
Muawia Khan |
Bug Description
Race condition hits when creating default security group which results in inconsistency between PLUMgrid controller and neutron and returns this Error:
SecurityGroupEx
We need to remove the strict checking of one default security group per tenant in the plugin and allow rollback on neutron as well as controller in case of any failure o take care of the inconsistency.
Changed in networking-plumgrid: | |
assignee: | nobody → Muawia Khan (muawia) |
description: | updated |
Changed in networking-plumgrid: | |
status: | New → Confirmed |
status: | Confirmed → In Progress |
Changed in networking-plumgrid: | |
importance: | Undecided → Critical |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/198873 /git.openstack. org/cgit/ stackforge/ networking- plumgrid/ commit/ ?id=cbd6e2f7932 d9d213c1150ab94 699ffba9a0b570
Committed: https:/
Submitter: Jenkins
Branch: master
commit cbd6e2f7932d9d2 13c1150ab94699f fba9a0b570
Author: Muawia Khan <email address hidden>
Date: Tue Jul 7 00:35:55 2015 +0500
Fix for race condition in security groups creation
There was a race condition in the creation of default security group,
which was exposed when neutron was able to create a default security
group and backend controller fails which results in inconsitency between
neutron and backend controller.
This fix will allow both neutron and backend controller to rollback
in case of any failure i.e. either on neutron side or backend
controller to maintain consistency between both. It also removes the
strict checking for one default security group per tenant and will allow
neutron to handle this scenario
Change-Id: Ic0de2596d723ce ba601d60371d644 f320d5e37be
Closes-Bug: 1471287