Security groups with source groups no longer work
Bug #1216720 reported by
Sam Morrison
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Critical
|
Vish Ishaya | ||
Grizzly |
Fix Released
|
Critical
|
Vish Ishaya |
Bug Description
The fix for bug #1184041 has a side affect of breaking security group linking via source groups.
Example:
Secgroup "Server" has rule
+------
| IP Protocol | From Port | To Port | IP Range | Source Group |
+------
| tcp | 8140 | 8140 | | client |
+------
Instance A is running and is associated with the "Server" secgroup
Now if a create a new instance with the "client" security group it should add a rule to instance A to all the new instance to talk to it.
This no longer gets added as it uses the cached version.
Changed in nova: | |
assignee: | nobody → ugvddm (271025598-9) |
Changed in nova: | |
assignee: | ugvddm (271025598-9) → nobody |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-3 → 2013.2 |
no longer affects: | nova/folsom |
To post a comment you must log in.
Might also affect Folsom/Grizzly as the fix was backported