yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1216720

Title:
  Security groups with source groups no longer work

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) folsom series:
  New
Status in OpenStack Compute (nova) grizzly series:
  Confirmed

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.

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