I had same symptom (trusty/icehouse). hitting metadata via the 169 address generated the same error. I turned on debug for metadata service and found I had my auth_url pointing to wrong place in metadata_agent.ini. I suspect you have checked all of these things already. If you suspect v4/v6 problem you could try changing your auth_url, etc to known bad values and see if behavior changes.
On Mon, May 19, 2014 at 12:13 AM, Martinx - ジェームズ <[email protected] > wrote: > I forgot to post my configuration details, here we go: > > > * Controller Node (psuaa-1 host): > > grep metadata /etc/nova/* > > --- > root@psuaa-1:~# grep metadata /etc/nova/nova.conf > metadata_host = 192.168.5.10 > metadata_listen = 192.168.5.10 > service_neutron_metadata_proxy = True > neutron_metadata_proxy_shared_secret = XXXYY > --- > > > * Network Node (psuab-1 host): > > cat /etc/neutron/metadata_agent.ini > > --- > [DEFAULT] > debug = True > verbose = True > > auth_url = http://psuaa-1.tcmc.com.br:5000/v2.0 > auth_region = sp-east-1 > admin_tenant_name = service > admin_user = neutron > admin_password = XXXZZ > > nova_metadata_ip = 192.168.5.10 > nova_metadata_port = 8775 > metadata_proxy_shared_secret = XXXYY > --- > > cat /etc/neutron/dhcp_agent.ini > > --- > [DEFAULT] > verbose = True > interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver > dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq > use_namespaces = True > dhcp_domain = tcmc.com.br > --- > > * Connectivity test: > > --- > root@psuab-1:~# telnet 192.168.5.10 8775 > Trying 192.168.5.10... > Connected to 192.168.5.10. > Escape character is '^]'. > --- > > NOTE: The value of auth_url entry, "http://psuaa-1.tcmc.com.br:5000/v2.0";, > is an IPv6-Only address. > > --- > root@psuab-1:~# telnet psuaa-1.tcmc.com.br 5000 > Trying 2804:290:4:dead::10... > Connected to psuaa-1.tcmc.com.br. > Escape character is '^]'. > --- > > > * Compute Node (psuah-1 host): > > grep metadata /etc/nova/nova.conf > > --- > root@psuah-1:~# grep metadata /etc/nova/nova.conf > metadata_host = 192.168.5.10 > service_neutron_metadata_proxy = True > neutron_metadata_proxy_shared_secret = XXXYY > --- > > > Tks! > Thiago > > > > On 19 May 2014 02:53, Martinx - ジェームズ <[email protected]> wrote: > >> Hello Stackers! >> >> I'm trying to deploy IceHouse with Ubuntu 14.04 and, almost everything is >> running just fine, except for Metadata, when I try to access it, using from >> within an Instance, the following command: >> >> >> "curl http://169.254.169.254/2009-04-04/instance-id"; >> >> >> I'm seeing the following error: "500 Internal Server Error" >> >> ScreenShot: http://i.imgur.com/wVEKeh0.png >> >> >> And, at the Network Node, the "Error 500" above, dumps the following >> messages at the logs: >> >> >> http://paste.openstack.org/show/80860/ >> >> >> BTW, I followed the Docs: >> http://docs.openstack.org/icehouse/install-guide/install/apt/content/ >> >> The only difference from the docs, is that my environment have IPv6 for >> APIs and Endpoints but, the Metadata Network, Projects subnets and GRE >> tunnels are still IPv4-Only... >> >> I appreciate any help! I'm not sure about how to debug it... Tks! >> >> Best, >> Thiago >> > > > _______________________________________________ > 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 > >
_______________________________________________ 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
