404 Error when retrieving metadata using DVR routers

[Armando Migliaccio]

This happens on master.

Steps to reproduce:

- usual devstack config will do
- boot a VM
- ssh to the VM
- curl http://169.254.169.254 from the console
- 404 Not Found error is reported

I would expect the metadata server response to come across correctly.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/112376

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/112376
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=338171c114743c0e03def04ef551231f0d9c93f8
Submitter: Jenkins
Branch: master

commit 338171c114743c0e03def04ef551231f0d9c93f8
Author: armando-migliaccio <email address hidden>
Date: Wed Aug 6 10:13:32 2014 -0700

    Fix 404 error fetching metadata when using DVR

    The metadata agent was unable to find networks
    attached to the DVR router because it was only
    filtering ports for 'centralized' routers.

    To fix the issue, this patch expands the search
    filters to include DVR router interfaces during
    the network lookup operation.

    The extra filter cause no evident performance
    loss while serving the request; a different
    approach would require to pass the router type
    around to narrow down the search filter, but it
    sounds like an overkill.

    Closes-bug: #1353271

    Change-Id: Iefbefa1ff300adad48ab9fc472d5eb1913fbe488

[uttam hoode (uttamhoode)]

Facing same issue on Kilo setup

Node1: Controller + Network + Compute (l3_agent.ini -> agent_type dvr_snat )
Node2: Compute (l3_agent.ini -> agent_type dvr)