yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => grizzly-3

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1078154

Title:
  nova baremetal overrides network card MAC addresses, interacts poorly
  with udev persistent rules

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  This interacts poorly with udev rules on Ubuntu that remember the MAC
  address of interfaces: the first boot will work as expected, but after
  a single reboot, eth0 will be missing because eth0 is 'remembered' as
  the original MAC address of the card, not the nova assigned random
  address.

  Similar issues can be predicted for Windows, other Linux distributions
  and most operating systems: manually assigned NIC MAC addresses are
  the exception, not the rule.

  The baremetal code was written to do this for consistency with nova VM
  based instances, but VM's are running with virtual hardware: there the
  NIC MAC address is not overriden by the operating system, but
  configured to be what nova expects in the hypervisor. There isn't a
  generic mechanism to do that for baremetal.

  A list discussion was held; the the most sensible answer, at least for
  hardware with real MAC addresses like PXE booting i386/amd64 class
  machines, is to not override the MAC address at all. However, this
  does entail the bare metal driver being able to set the MAC address
  for an instance rather than nova dynamically allocating it.

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