yahoo-eng-team team mailing list archive

[shihanzhang <shihanzhang@xxxxxxxxxx>]

Public bug reported:

reproduce step:

1.  VM1 in security group A
2.  VM2 in security group B
3.  security group B can access security group A
4.  update VM1 to security group C

I found that VM1 ip address was still in ipset members which belongs to
security group A, but now VM1 was already in security group C

** Affects: neutron
     Importance: Undecided
     Assignee: shihanzhang (shihanzhang)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => shihanzhang (shihanzhang)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1458786

Title:
  Update port security group, relevant ipset member can't be updated

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  reproduce step:

  1.  VM1 in security group A
  2.  VM2 in security group B
  3.  security group B can access security group A
  4.  update VM1 to security group C

  I found that VM1 ip address was still in ipset members which belongs
  to security group A, but now VM1 was already in security group C

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