Richard Raseley wrote: > Teclus D'souza wrote: >> wget: can't connect to remote host (169.254.169.254): Network is >> unreachable > > Teclus, > > The error above potentially indicates a problem with the Neutron > metadata service. Can you ensure that this service is running in the > appropriate place? Once running, this service will spawn a > 'neutron-ns-metadata-proxy' process for each network deployed within > Neutron. If you execute the command `ps aux | grep -i > neutron-ns-metadata-proxy` on the server where the metadata service is > running you should get an output of all the currently running metadata > proxy processes. Each of these lines will have a `--network_id=` flag > associated with it which will contain the Neutron network ID to which it > is associated. > > If all that looks good, please post the contents of the > `/var/log/neutron/metadata-agent.log` as well as the contents of any > `/var/log/neutron/neutron-ns-metadata-proxy-*.log` files to > https://gist.github.com (or similar) and respond to this post so we can > look further. > > Regards, > > Richard Raseley > > SysOps Engineer > Puppet Labs Correction, it is the Neutron DHCP Agent which spawns these `neutron-ns-metadata-proxy` processes, not the Neutron Metadata Agent.
Regards, Richard Raseley SysOps Engineer Puppet Labs
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
