yahoo-eng-team team mailing list archive

[OpenStack Infra <1572171@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/307850
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=93fde493aceb47d74b84c7c8665bba5bd8ea1797
Submitter: Jenkins
Branch:    master

commit 93fde493aceb47d74b84c7c8665bba5bd8ea1797
Author: Roey Chen <roeyc@xxxxxxxxxx>
Date:   Tue Apr 26 08:42:54 2016 -0700

    network: Fix nova boot with multiple security-groups
    
    Booting an instance with 'default' + other security-groups doesn't
    apply the 'default' security-group on the instance.
    Nova is required to remove the 'default' security-group from the request
    to Neutron when it's the only security-group that should be applied on
    the instance.
    This bug is a result of change
    I630008a9733624a9d9b59b7aa3b8b2a3f8985d61.
    
    Closes-Bug: #1572171
    Change-Id: I3eb685f4d82615d3ebd25e7471de47129c78c86a


** Changed in: nova
       Status: In Progress => 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/1572171

Title:
  Booting an instance with default + other security-groups does not work
  as expected

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  booting an instance with multiple security-groups where one of the
  security-groups is the 'default' security-groups, will not apply the
  default security group to the instance.

  E.g -

  $ nova boot ... --security-groups default,MYSG   VM1

  Expected result:  VM1 should have both 'default' and MYSG security-groups.
  Actual result: VM1 has only MYSG security-group

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