yahoo-eng-team team mailing list archive

[ZongKai LI <lzklibj@xxxxxxxxxx>]

it's neutron's problem.
the operation in bug description is floating ip re-assignment, this can depart into two steps, disassociate from origin port, associate to new port; when re-assign floating ip, network changes happened on two(origin, new) instance's port, but neutron only send event for new instance port;
add code ensure neutron will first send event for origin/disassociate one, then send event for new/associate one, will fix this.

** Project changed: nova => neutron

** Changed in: neutron
       Status: New => Fix Committed

** Changed in: neutron
     Assignee: (unassigned) => ZongKai LI (lzklibj)

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

Title:
  nova list show incorrect when neutron re-assign floatingip

Status in OpenStack Neutron (virtual network service):
  Fix Committed

Bug description:
  boot more several instances, create a floatingip, when re-assign the floatingip to multi instances, nova list will show incorrect result.
  >>>neutron floatingip-associate floatingip-id instance0-pord-id
  >>>neutron floatingip-associate floatingip-id instance1-port-id
  >>>neutron floatingip-associate floatingip-id instance2-port-id
  >>>nova list
  (nova list result will be like:)
  --------------------------
  instance0      fixedip0,  floatingip
  instance1      fixedip1,  floatingip
  instance2      fixedip2,  floatingip

  instance0,1,2, they all have floatingip, but run "neutron floatingip-list", we can see it only bind to instance2.
  another situation is that after a few time(half a min, or longer), "nova list" can show correct result.
  ---------------------------
  instance0      fixedip0
  instance1      fixedip1
  instance2      fixedip2,  floatingip

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