yahoo-eng-team team mailing list archive

[Armando Migliaccio <1581220@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

It looks like steps to create server as outlined in [2] lead to the same
FIP being associated to two individual ports [1] (offending fip
f1169479-7d88-4526-a60a-82f18b617077). It looks like two interleaving
calls to do FIP association by port-id will end up clashing. This has
been reproduced in Kilo, but we would need to find out if the race is
still possible in newer versions.

[1] https://gist.github.com/cloudnull/d90eff7efc524844d8d3504fea8fa419
[2] https://gist.github.com/cloudnull/2f3931e51062dc7b325faf9a24974006

** Affects: neutron
     Importance: High
         Status: Confirmed

** Summary changed:

- same floating ip can be associated to separate ports
+ race leads same floating ip to be associated to separate ports

** Changed in: neutron
   Importance: Undecided => High

** Changed in: neutron
       Status: New => Confirmed

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

Title:
  race leads same floating ip to be associated to separate ports

Status in neutron:
  Confirmed

Bug description:
  It looks like steps to create server as outlined in [2] lead to the
  same FIP being associated to two individual ports [1] (offending fip
  f1169479-7d88-4526-a60a-82f18b617077). It looks like two interleaving
  calls to do FIP association by port-id will end up clashing. This has
  been reproduced in Kilo, but we would need to find out if the race is
  still possible in newer versions.

  [1] https://gist.github.com/cloudnull/d90eff7efc524844d8d3504fea8fa419
  [2] https://gist.github.com/cloudnull/2f3931e51062dc7b325faf9a24974006

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