openstack team mailing list archive

[Sharif Islam <islamsh@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I have noticed another weird issue with dnsmasq which might be related
to the problem.

# tail -1 /etc/nova/nova.conf
- --dnsmasq_config_file=/etc/dnsmasq.conf

#killall dnsmasq
# /etc/init.d/openstack-nova-network restart
Stopping OpenStack Nova Network Controller:                [  OK  ]
Starting OpenStack Nova Network Controller:                [  OK  ]
# ps -eaf|grep dnsmasq
nobody    3385     1  0 12:05 ?        00:00:00 dnsmasq --strict-order
- --bind-interfaces --conf-file= --domain=novalocal
- --pid-file=/local/nova/networks/nova-br100.pid --listen-address=10.0.1.1
- --except-interface=lo --dhcp-range=10.0.1.2,static,120s
- --dhcp-lease-max=256
- --dhcp-hostsfile=/local/nova/networks/nova-br100.conf
- --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
root      3386  3385  0 12:05 ?        00:00:00 dnsmasq --strict-order
- --bind-interfaces --conf-file= --domain=novalocal
- --pid-file=/local/nova/networks/nova-br100.pid --listen-address=10.0.1.1
- --except-interface=lo --dhcp-range=10.0.1.2,static,120s
- --dhcp-lease-max=256
- --dhcp-hostsfile=/local/nova/networks/nova-br100.conf
- --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro


The --conf-file is not taking the dnsmasq_config_file=/etc/dnsmasq.conf
flag.

I tried this particular change in another identical machine and was able
to update dnsmasq properly after restarting nova-network that is
- --conf-file showing the dnsmasq.conf. So something is messed up in this
machine.

Any other suggestions?

- --sharif







On 10/10/2011 05:23 PM, Sharif Islam wrote:
> On 10/10/2011 05:01 PM, Jason Kölker wrote:
> 
>>> nameserver 10.0.1.1
>>>
>>> How does nova assign the nameserver to the VMs? Can I change it someone
>>> so it has 8.8.4.4?
> 
> 
>> I assume you are using Vlan or Flatdhcp? If so add --dns-server=8.8.4.4
>> to your flags file. The network managers that use dnsmasq do not respect
>> the db entries.
> 
> 
> Yes, I am using FlatDCHP. I am still using cactus release btw.
> 
> Unfortunately, this fix didn't work.
> 
> # cat /etc/nova/nova.conf|grep dns
> --dns-server=8.8.4.4
> 
> I restarted the services. Also deleted the network and created it again
> just in case.
> 
> 
> root@i-0000049d:~# ping google.com
> ping: unknown host google.com
> root@i-0000049d:~# ping 72.14.204.147
> PING 72.14.204.147 (72.14.204.147) 56(84) bytes of data.
> 64 bytes from 72.14.204.147: icmp_req=1 ttl=54 time=33.0 ms
> 64 bytes from 72.14.204.147: icmp_req=2 ttl=54 time=33.7 ms
> ^C
> --- 72.14.204.147 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 1001ms
> rtt min/avg/max/mdev = 33.079/33.394/33.709/0.315 ms
> root@i-0000049d:~# cat /etc/resolv.conf
> domain novalocal
> search novalocal
> nameserver 10.0.1.1
> 
> 
> 
> # ps -aef|grep dnsmasq
> nobody    9850     1  0 14:32 ?        00:00:00 dnsmasq --strict-order
> --bind-interfaces --conf-file= --domain=novalocal
> --pid-file=/local/nova/networks/nova-br100.pid --listen-address=10.0.1.1
> --except-interface=lo --dhcp-range=10.0.1.2,static,120s
> --dhcp-lease-max=256
> --dhcp-hostsfile=/local/nova/networks/nova-br100.conf
> --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
> root      9851  9850  0 14:32 ?        00:00:00 dnsmasq --strict-order
> --bind-interfaces --conf-file= --domain=novalocal
> --pid-file=/local/nova/networks/nova-br100.pid --listen-address=10.0.1.1
> --except-interface=lo --dhcp-range=10.0.1.2,static,120s
> --dhcp-lease-max=256
> --dhcp-hostsfile=/local/nova/networks/nova-br100.conf
> --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro
> 
> 
> --sharif

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


- -- 
Sharif Islam
Senior Systems Analyst/Programmer
FutureGrid (http://futuregrid.org)
Pervasive Technology Institute, Indiana University Bloomington
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOlGoDAAoJEACffes9SivFCBcH/A2qw9Gw/tsPla0XJa/cjvuK
QNhW8xe2FKR52IbbGlCMGjb1+eUQkJ3NfGudcYQJOEPwXLifNWx+IzgeEWIicL+f
0ao41v1IDpP+08n+aFjdwWPCXkmsP8+iSI6+AO7IY814CWVoTBtrvOX8DFPioqGD
alwdJ3Sj/6f1fsQAY4J3BzNIrCQweqrzO4flrw8raWqDWHvsfZ/pnvgwIOKvALaj
7sT8kE/xzds6UUu5daikZwKFr4I9rgy8F/dbW6aCqAnrkIaEwUCxlde7vEb5aOyU
0/8+4vfYUcrnGVrSkiRWEX5kpI8T+0TX0B7QHVJ4gB4WVS9Q01xTC4RCwPQtMqQ=
=vDlN
-----END PGP SIGNATURE-----