Don't get metadata from nova-api

Asked by Heiko Krämer

Hey Guys,

i'm using UEC image with ubuntu 11.10.
If i run an instance i get every time

DataSourceEc2.py[WARNING]: 'http://169.254.169.254' failed: url error [time out].
I tried with other DMZ-Host (pub-ip) and other my_ip-Flag in nova.conf, but it wasn't successfully.

The Nova-Api are reachable on a public and internal interface (pub and private net).
All Services are distributed, so i have a server for nova-api, DB, compute. On each compute node runs a network-manager too.

I've studied the tcpdump and the routing logs, and i see the this request above have no route (no really working route) to the api.

Btw. i can ping each started instance!

####################################################
My IP-Tables:
http://pastebin.com/S91mDe7q
####################################################
IP-Tables NAT:
http://pastebin.com/k99F8Mes

####################################################
IP addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet 169.254.169.254/32 scope link lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 100
    link/ether 00:30:48:d3:4f:32 brd ff:ff:ff:ff:ff:ff
    inet 78.xxx.xxx.198/26 brd 78.xxx.xxx.255 scope global eth0
    inet6 fe80::230:ffff:fffff:fff32/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:30:48:d3:4f:33 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.14/24 brd 192.168.0.255 scope global eth1
    inet6 fe80::230:48ff:fed3:4f33/64 scope link
       valid_lft forever preferred_lft forever
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 06:71:0e:04:0c:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
5: vlan100@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 02:16:3e:66:5c:07 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::16:3eff:fe66:5c07/64 scope link
       valid_lft forever preferred_lft forever
8: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 02:16:3e:66:5c:07 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.21/24 brd 10.0.0.255 scope global br100
    inet6 fe80::16:3eff:fe66:5c07/64 scope link
       valid_lft forever preferred_lft forever
23: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500
    link/ether fe:16:3e:1a:bc:bf brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc16:3eff:fe1a:bcbf/64 scope link
       valid_lft forever preferred_lft forever

#############################################
VLAN:

vlan100 VID: 100 REORDER_HDR: 1 dev->priv_flags: 4001
         total frames received 5208
          total bytes received 362584
      Broadcast/Multicast Rcvd 5177

      total frames transmitted 1129
       total bytes transmitted 76122
Device: eth1
INGRESS priority mappings: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0
 EGRESS priority mappings:

#############################################
Bridge:
bridge name bridge id STP enabled interfaces
br100 8000.02163e2c6463 no vlan100
virbr0 8000.000000000000 yes

############################################
Nova.conf

--daemonize=1
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--network_manager=nova.network.manager.VlanManager
--public_interface=eth0
--vlan_interface=eth1
--fixed_range=10.0.0.0/8
--cc_host=78.xxx.xxx.202
--routing_source_ip=192.168.0.14
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--s3_host=78.xxx.xxx.202
--rabbit_host=192.168.0.3
--ec2_url=http://78.xxxx.xxx.202:8773/services/Cloud
--ec2_port=8773
--ec2_dmz_host=192.168.0.3
--FAKE_subdomain=ec2
--keystone_ec2_url=http://192.168.0.3:5000/v2.0/ec2tokens
--sql_connection=mysql://nova:xxxx@192.168.0.102/nova
--image_service=nova.image.glance.GlanceImageService
--glance_api_servers=192.168.0.103:9292
--iscsi_ip_prefix=192.168.
--allow_admin_api
--verbose
--debug
--osapi_extensions_path=/var/www/openstackx/extensions
--api_paste_config=/etc/nova/api-paste.ini
--multi_host=True
--my_ip=192.168.0.14

I spent now many time in this but without success :(, i hope anyone have a hint for me.

Greetings
Heiko

Question information

Language:
English Edit question
Status:
Expired
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Heiko Krämer (foexle) said :
#1

More TCP-Dumps:
#############################
Compute-Node:

eth1:
11:19:51.548953 IP 192.168.0.3.8773 > 192.168.0.14.38404: Flags [F.], seq 196, ack 151, win 122, options [nop,nop,TS val 195646033 ecr 4294906320], length 0

11:19:51.549024 IP 192.168.0.14.38404 > 192.168.0.3.8773: Flags [.], ack 196, win 490, options [nop,nop,TS val 4294906344 ecr 195646033], length 0

11:19:51.549525 IP 192.168.0.14.38403 > 192.168.0.3.8773: Flags [F.], seq 151, ack 197, win 490, options [nop,nop,TS val 4294906344 ecr 195645007], length 0

11:19:51.549651 IP 192.168.0.3.8773 > 192.168.0.14.38403: Flags [.], ack 152, win 122, options [nop,nop,TS val 195646033 ecr 4294906344], length 0

11:19:51.586517 IP 192.168.0.14.38404 > 192.168.0.3.8773: Flags [.], ack 197, win 490, options [nop,nop,TS val 4294906354 ecr 195646033], length 0

br100:

11:20:21.264227 IP 10.0.0.47.38410 > 192.168.0.3.8773: Flags [S], seq 2984900303, win 14600, options [mss 1460,sackOK,TS val 4294913773 ecr 0,nop,wscale 5], length 0

11:20:21.264727 IP 10.0.0.47.38410 > 192.168.0.3.8773: Flags [.], ack 2790093483, win 457, options [nop,nop,TS val 4294913773 ecr 195653462], length 0

11:20:21.264882 IP 10.0.0.47.38410 > 192.168.0.3.8773: Flags [P.], seq 0:150, ack 1, win 457, options [nop,nop,TS val 4294913773 ecr 195653462], length 150

###################################
Api (eth1)

11:20:45.797743 IP 192.168.0.3.8773 > 192.168.0.14.38414: Flags [F.], seq 196, ack 151, win 122, options [nop,nop,TS val 195659595 ecr 4294919882], length 0

11:20:45.797915 IP 192.168.0.14.38414 > 192.168.0.3.8773: Flags [.], ack 196, win 490, options [nop,nop,TS val 4294919906 ecr 195659595], length 0

11:20:45.798414 IP 192.168.0.14.38413 > 192.168.0.3.8773: Flags [F.], seq 151, ack 197, win 490, options [nop,nop,TS val 4294919906 ecr 195658069], length 0

11:20:45.798430 IP 192.168.0.3.8773 > 192.168.0.14.38413: Flags [.], ack 152, win 122, options [nop,nop,TS val 195659596 ecr 4294919906], length 0

11:20:45.834510 IP 192.168.0.14.38414 > 192.168.0.3.8773: Flags [.], ack 197, win 490, options [nop,nop,TS val 4294919916 ecr 195659595], length 0

So it seem's the route back to the instance are not correct. The request arrives the compute node but not the instance.

Revision history for this message
Launchpad Janitor (janitor) said :
#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.