yahoo-eng-team team mailing list archive

[OpenStack Infra <1581918@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/316615
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e45add7b07e5c72c43047d18e10af1c4ae307b0f
Submitter: Jenkins
Branch:    master

commit e45add7b07e5c72c43047d18e10af1c4ae307b0f
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Wed May 11 09:55:49 2016 -0700

    Restart dsnmasq on any network subnet change
    
    When a new subnet is added to a network, the network cache
    is updated with the list of subnets regardless of which ones
    have DHCP enabled. This changes the index order of the subnet
    list which means that the tags used for each subnet change.
    
    This means we must restart the process because the opts file
    will be using different tags than the process args. This patch
    implements that change. It also sorts the subnets on the RPC
    side so the agent indexes don't change if subnets aren't
    added/deleted.
    
    The previous logic was only restarting the process when DHCP
    enabled subnets changed, which meant that adding a DHCP disabled
    subnet would break the association between the opts file tags and
    the process arg tags, which led to the reported bug.
    
    Closes-Bug: #1581918
    Change-Id: If1452c0e8fe95eb94cd78c7a05b57aead75662b5


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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