yahoo-eng-team team mailing list archive

[Phil Day <1118608@xxxxxxxxxxxxxxxxxx>]

https://review.openstack.org/#/c/21529/

** This bug is no longer a duplicate of bug 1122316
   Restarting nova-compute with source groups lead to traceback.

** Changed in: nova
       Status: In Progress => Fix Committed

-- 
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/1118608

Title:
  source-group security group rule not working with nova networking

Status in OpenStack Compute (Nova):
  Fix Committed

Bug description:
  Using a source-group type of rule with nova networking leads to VM not
  spawning (going into ERROR), when the source and destination group are
  the same.

  Steps:
  - Fresh devstack with default services (n-net and not quantum)
  -  nova secgroup-create nasty nasty
  - nova secgroup-add-group-rule nasty nasty icmp -1 -1
  -  nova boot --image 68e97f3c-f160-48f9-9ce1-b6d8871c1f8b --flavor 1 --security-group nasty testvm0001

  VM goes into error.
  The issue is reproducible consistently.

  Using Grizzly-2

  ubuntu@devstack02:/opt/stack/nova$ git log -1 | head -2
  commit 9ba00e5ab8eec49fddd9ca03fdd9c07c41b088b7
  Merge: d2dad24 905b784

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