no ssh or ping to instance and vnc console shows wget: can't connect to remote host (169.254.169.254): No route to host
Setup: Openstack Grizzly (1 Control Node, 1 Compute Node) Physical. Ubuntu 12.04
NIC 2 physical interface on each node. (eth0,eth1).
Nova-network used.
Instance launched and assigned with IP (fixed and Floating). But while accessing it it does not ping or ssh. Error in Console shown.
wget: can't connect to remote host (169.254.169.254): No route to host
the respective settings are:
----------
**Compute node : ifconfig details**
----------
br100 Link encap:Ethernet HWaddr 38:60:77:66:8b:4c
inet addr:192.168.80.3 Bcast:192.168.80.255 Mask:255.255.255.0
inet6 addr: fe80::bccd:16ff:fe1d:12db/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17511 errors:0 dropped:0 overruns:0 frame:0
TX packets:3282 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:898656 (898.6 KB) TX bytes:333133 (333.1 KB)
eth0 Link encap:Ethernet HWaddr cc:b2:55:ba:b7:be
inet addr:192.168.80.201 Bcast:192.168.80.255 Mask:255.255.255.0
inet6 addr: fe80::ceb2:55ff:feba:b7be/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25481 errors:0 dropped:0 overruns:0 frame:0
TX packets:31706 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12231170 (12.2 MB) TX bytes:6137505 (6.1 MB)
eth1 Link encap:Ethernet HWaddr 38:60:77:66:8b:4c
inet addr:10.1.1.121 Bcast:10.1.1.255 Mask:255.255.255.0
inet6 addr: fe80::3a60:77ff:fe66:8b4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17579 errors:0 dropped:0 overruns:0 frame:0
TX packets:3470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1154032 (1.1 MB) TX bytes:357327 (357.3 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:849 errors:0 dropped:0 overruns:0 frame:0
TX packets:849 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:67298 (67.2 KB) TX bytes:67298 (67.2 KB)
vnet0 Link encap:Ethernet HWaddr fe:16:3e:0b:bd:60
inet6 addr: fe80::fc16:3eff:fe0b:bd60/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:187 errors:0 dropped:0 overruns:0 frame:0
TX packets:11889 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:9246 (9.2 KB) TX bytes:720680 (720.6 KB)
vnet1 Link encap:Ethernet HWaddr fe:16:3e:86:72:ca
inet6 addr: fe80::fc16:3eff:fe86:72ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:733 errors:0 dropped:0 overruns:0 frame:0
TX packets:11889 errors:0 dropped:0 ... (more) 
Hi, do you get any warnings in the quantum log? I have a very similar problem and also get the following warning when launching the instance:
2013-09-17 16:50:58 WARNING [quantum.db.agentschedulers_db] Fail scheduling network {'status': u'ACTIVE', 'subnets': [u'792aa923-a38a-4918-a108-bff0ec11f6f5'], 'name': u'fe_net01', 'provider:physical_network': u'physnet2', 'admin_state_up': True, 'tenant_id': u'8e6aa410c7e9464fa4d32b14f77f9571',
'provider:network_type': u'vlan', 'router:external': False, 'shared': False, 'id': u'409c22e7-d1ca-46d2-ad49-6e26f26d0286', 'provider:segmentation_id': 401L}
This seems like an issue for many people so I've filed a bug: https://bugs.launchpad.net/neutron/+bug/1226651
The question is about nova-network, not quantum.