yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

Public bug reported:

When a network contains several subnets (especially ipv4 + ipv6) DHCP
agent may spawn dnsmasq incorrectly, so tag in the command line (--dhcp-
range) will not match the tag in opts file.

This leads to a state when dnsmasq sends it's IP address as a default
gateway.

As a side effect, VM's floating ip snat traffic begin to flow through
dhcp namespace of the server that has given an ip address to that VM.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-ipam-dhcp

** Tags added: l3-ipam-dhcp

** Description changed:

  When a network contains several subnets (especially ipv4 + ipv6) DHCP
- agent may spawn dnsmasq incorrectly, so tag in command line (--dhcp-
+ agent may spawn dnsmasq incorrectly, so tag in the command line (--dhcp-
  range) will not match the tag in opts file.
  
  This lead to a state when dnsmasq sends it's IP address as a default
  gateway.
  
  As a side effect, VM's floating ip snat traffic begin to flow through
  dhcp namespace of the server that has given an ip address to that VM.

** Description changed:

  When a network contains several subnets (especially ipv4 + ipv6) DHCP
  agent may spawn dnsmasq incorrectly, so tag in the command line (--dhcp-
  range) will not match the tag in opts file.
  
- This lead to a state when dnsmasq sends it's IP address as a default
+ This leads to a state when dnsmasq sends it's IP address as a default
  gateway.
  
  As a side effect, VM's floating ip snat traffic begin to flow through
  dhcp namespace of the server that has given an ip address to that VM.

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

Title:
  Sometimes DHCP agent spawns dnsmasq incorrectly

Status in neutron:
  New

Bug description:
  When a network contains several subnets (especially ipv4 + ipv6) DHCP
  agent may spawn dnsmasq incorrectly, so tag in the command line
  (--dhcp-range) will not match the tag in opts file.

  This leads to a state when dnsmasq sends it's IP address as a default
  gateway.

  As a side effect, VM's floating ip snat traffic begin to flow through
  dhcp namespace of the server that has given an ip address to that VM.

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