yahoo-eng-team team mailing list archive

[Chuck Carlino <ccarlino@xxxxxx>]

The problem is a race where after the address is removed from the old
port and before it's assigned to the new port, it could be allocated to
another port.

** Changed in: neutron
       Status: Opinion => In Progress

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

Title:
  mac_address port attribute is read-only

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  Ironic uses Neutron for IPAM - IP address allocation and DHCP, same as
  nova with e.g. KVM or Xen. Unlike a virtual machine hypervisor,
  Ironics real machines sometimes develop hardware faults, and parts
  need to be replaced - and when that happens the port MAC changes.
  Having the port's mac address be read-only makes this much more
  intrusive than it would otherwise be - we have to tear down and
  rebuild the whole machine, rather than just replace the card and tell
  Neutron the new MAC.

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