yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1400286@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  Subnet should allow for disabling DNS nameservers (instead of pushing
  dhcp ip as default)

Status in OpenStack Neutron (virtual network service):
  Expired

Bug description:
  When connecting a VM to more than 1 network interface, defaults of the
  second subnet will override user-defined settings of the first
  (usually primary) interface.

  Reproduce:
  1. create a VM with 2 network interfaces where:
      eth0 - subnet with a GW, and a custom DNS nameserver
      eth1 - secondary network where subnet is created with default settings, dhcp enabled
  NOTE: most images will require manually  requesting DHCP on eth1
  2. check routing and DNS details on VM.
      custom settings from primary subnet's DNS, and default GW have been overridden by secondary subnet's defaults

  Workarounds:
  1. reverse network settings so that primary interface sends DHCP request last.
      - problematic because usually the most important network and NIC should be defined first. Also, some VMs might be connected only to primary, so this would create inconsistencies between VMs in the same network
  2. Manually disable defaults on secondary subnet:
      - Works for GW.
      - Doesn't work for DNS, since Neutron configures dnsmasq to push DHCP port's IP when no DNS nameserver is defined
  3. Manually set secondary subnet's DNS to match primary's.
      - Not all users have access to the data of all other subnets. Primary network might have been created by another user

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