Is it possible to get Quantum working with nova metdata service?

I'm running Folsom with the Ryu plugin, and I can't seem to get my VMs to boot because they are constantly trying to get to the Nova metadata service. I've followed directions here, and none of them work:

http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html

e.g. I can't ping (using net namespaces) the metadata_ip, and I can't ping the un-NAT'ed IP either on the host. I'm using devstack with a multinode setup, but running Quantum, L3, and Nova metadata on the same host.

The console logs for my VM looks like this:

info: initramfs: up at 1.14
[ 1.158321] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
info: copying initramfs to /dev/vda
[ 1.204990] EXT3-fs (vda): warning: checktime reached, running e2fsck is recommended
info: initramfs loading root from /dev/vda
info: /etc/init.d/rc.sysinit: up at 2.08
[ 2.087313] EXT3-fs (vda): warning: checktime reached, running e2fsck is recommended
Starting logging: OK
Initializing random number generator... done.
Starting network...
udhcpc (v1.18.5) started
Sending discover...
Sending select for 10.0.0.3...
Lease of 10.0.0.3 obtained, lease time 120
deleting routers
route: SIOCDELRT: No such process
adding dns 10.0.0.2
cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id
wget: can't connect to remote host (169.254.169.254): Connection timed out
cloud-setup: failed 1/30: up 2.28. request failed
wget: can't connect to remote host (169.254.169.254): Connection timed out
cloud-setup: failed 2/30: up 192.71. request failed

Any ideas here? Searching turned up various things like this:

https://bugs.launchpad.net/nova/+bug/719798

But that looks REALLY old and in fact adding 169.254.169.254 to eth1 didn't do anything to help the situation.