yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1170793] Re: dnsmasq returns its own IP as gateway

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 29 May 2013 11:06:11 -0000
Reply-to: Bug 1170793 <1170793@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

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

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

Title:
  dnsmasq returns its own IP as gateway

Status in OpenStack Quantum (virtual network service):
  Fix Released

Bug description:
  I'm getting a weird behaviour. When I run a VM, it gets the address of DHCP server (dnsmasq) as the default gateway !!!!
  My install is as follow :
    - two physical nodes, each with two NICs (one for management network, and the other for Data network (VMs) )
    - OS : CentOS 6.4
    - L2 plugin : Linuxbridge
    - namespaces=False
    - dhcp-agent is running on the controller node (all openstack services : nova, glance, cinder, quantum-server, ...)
    - l3-agent is runnig on the compute node
  Because of the misconfigured  gateway, I can't access to my VMs using floating IPs, till I change the default gateway myself(I can access the VMs using their fixed IPs)
  any idea what's wrong?
  if you need any additional information, you can ask.
  thanks in advance

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