yahoo-eng-team team mailing list archive

[Dongcan Ye <hellochosen@xxxxxxxxx>]

Public bug reported:

Problem Description
=============================

1.  Create an instance,  fixed_ip is allocating by dhcp agent. 
2.  Associate a floating_ip to the instance,  then ssh or ping floating_ip.
3.  Delete the instance, floating_ip is disassociated.
4.  Create another instance, specify the same fixed_ip in step 1 which dhcp  agent auto allocated.
5.  Associate the same floating_ip in step 2 , then ssh or ping floating_ip will failed.

The reason for this issue is the arp entry in router namespace is old
instance mac address.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  floating ip can‘t work because instance mac address conflict

Status in neutron:
  New

Bug description:
  Problem Description
  =============================

  1.  Create an instance,  fixed_ip is allocating by dhcp agent. 
  2.  Associate a floating_ip to the instance,  then ssh or ping floating_ip.
  3.  Delete the instance, floating_ip is disassociated.
  4.  Create another instance, specify the same fixed_ip in step 1 which dhcp  agent auto allocated.
  5.  Associate the same floating_ip in step 2 , then ssh or ping floating_ip will failed.

  The reason for this issue is the arp entry in router namespace is old
  instance mac address.

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