[Openstack-operators] Running crazy with Essex, multi_host, nova-network-ha, nova-api-metadata, VMs can't reach metadata nor respond through floating ip

Gui Maluf guimalufb at gmail.com
Tue Dec 18 20:52:53 UTC 2012


Countless times I'm here trying to make my openstack runnig! So here we go
again!

My set up is a nova-network-ha<http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html>,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller runs all of this and the rest of things it should run.

So I'm facing many problems in my setup. The main thing is: iptables rules
are meaningless, they just doesnt work. VMs can't reach metadata, and
floating ip SNAT/DNAT is not pointing to VM.

I will put the max of info I can here.

root at oxala:~# nova-manage service
list

Binary           Host                                 Zone
Status     State Updated_At
nova-compute     xango                                nova
enabled    :-)   2012-12-18 20:34:21
nova-network     xango                                nova
enabled    :-)   2012-12-18 20:34:20
nova-compute     oxossi                               nova
enabled    :-)   2012-12-18 20:34:15
nova-network     oxossi                               nova
enabled    :-)   2012-12-18 20:34:20
nova-volume      oxossi                               nova
enabled    :-)   2012-12-18 20:34:18
nova-volume      xango                                nova
enabled    :-)   2012-12-18 20:34:19
nova-consoleauth oxala                                nova
enabled    :-)   2012-12-18 20:34:24
nova-scheduler   oxala                                nova
enabled    :-)   2012-12-18 20:34:25
nova-cert        oxala                                nova
enabled    :-)   2012-12-18 20:34:25
nova-volume      oxala                                nova
enabled    :-)   2012-12-18 20:34:25
nova-network     oxala                                nova
enabled    :-)   2012-12-18 20:34:17
nova-compute     oxala                                nova
enabled    :-)   2012-12-18 20:34:10

*controller nova.conf*
#NETWORK
--allow_same_net_traffic=true
--network_manager=nova.network.manager.FlatDHCPManager
--firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=10.5.5.32/27
--network_size=32
--flat_network_dhcp_start=10.5.5.33
--my_ip=200.131.6.250
--multi_host=True
#--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--force_dhcp_release
--ec2_private_dns_show
--routing_source_ip=$my_ip

*nodes nova.conf*
{same network configs}
--my_ip=200.131.6.248
--multi_host=True
--enabled_apis=ec2,osapi_compute,osapi_volume,metadata
--routing_source_ip=$my_ip

***controller iptables -L -vn && **iptables -L -vn* *-t nat*
http://paste.openstack.org/show/mkWZTYI6cKHR4qUWbOUz/
*node* *iptables -L -vn && **iptables -L -vn* *-t nat
*http://paste.openstack.org/show/28384/*
**
*
*controller ip a*
http://paste.openstack.org/show/W2vrVtost2EP2u62iZwp/
root at oxala:~# route
Tabela de Roteamento IP do Kernel
Destino         Roteador        MáscaraGen.    Opções Métrica Ref   Uso
Iface
default         200.131.6.129   0.0.0.0         UG    100    0        0 eth0
10.5.5.32       *               255.255.255.224 U     0      0        0
br100
200.131.6.128   *               255.255.255.128 U     0      0        0 eth0

*node ip a
*http://paste.openstack.org/show/S44TL3sznIztNCO3s8p2/*
*root at oxossi:~# route
Tabela de Roteamento IP do Kernel
Destino         Roteador        MáscaraGen.    Opções Métrica Ref   Uso
Iface
default         200.131.6.129   0.0.0.0         UG    100    0        0 eth0
10.5.5.32       *               255.255.255.224 U     0      0        0
br100
200.131.6.128   *               255.255.255.128 U     0      0        0 eth0
*

*
*And finnaly the error throw out by the vm when running on Nodes.

*

ci-info: lo    : 1 127.0.0.1       255.0.0.0       .

ci-info: eth0  : 1 10.5.5.53       255.255.255.224 fa:16:3e:69:cb:d2

ci-info: route-0: 0.0.0.0         10.5.5.35       0.0.0.0         eth0   UG

ci-info: route-1: 10.5.5.32       0.0.0.0         255.255.255.224 eth0   U

cloud-init start running: Tue, 18 Dec 2012 20:34:09 +0000. up 4.02 seconds

2012-12-18 20:34:15,967 - util.py[WARNING]:
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[6/120s]: url error [[Errno 113] No route to host]


I really don't know what to do anymore. This only happen on nodes, on
cloudcontroller all instance run smoothly. they get the floatip, metadata
service, etc.

I thought the nova-network-HA would give me less headache but is happening
the opposite. I would really appreciate if someone could help me!

Thanks in advance!
-- 
*guilherme* \n
\t *maluf*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20121218/678fd7a4/attachment.html>


More information about the OpenStack-operators mailing list