Problem with metadata

asked 2014-03-02 21:44:15 -0500

anonymous user

Anonymous

I'm having some problems setting up metadata service in my Openstack Installation that is deployed by one controller node, one network node and two compute nodes.

For example, I'm trying to launch an Ubuntu cloud-image and I have the following error in the log,

ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
ci-info: eth0  : 1 10.0.6.5        255.255.255.0   fa:16:3e:84:9f:3d
ci-info: route-0: 0.0.0.0         10.0.6.1        0.0.0.0         eth0   UG
ci-info: route-1: 10.0.6.0        0.0.0.0         255.255.255.0   eth0   U
cloud-init start running: Mon, 03 Mar 2014 03:37:17 +0000. up 17.31 seconds
2014-03-03 03:37:18,389 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: http error [404]
2014-03-03 03:37:20,206 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: http error [404]
2014-03-03 03:37:22,277 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]: http error [404]

My nova.conf is,

[DEFAULT]
auth_strategy=keystone
rpc_backend = nova.rpc.impl_kombu
rabbit_host = 192.168.82.11
rabbit_password = pfc
my_ip=192.168.82.13
vncserver_listen=0.0.0.0
novncproxy_base_url=http://138.4.18.11:6080/vnc_auto.html
vncserver_proxyclient_address=192.168.82.13
glance_host=192.168.82.11
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
libvirt_use_virtio_for_bridges=True
connection_type=libvirt
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
volumes_path=/var/lib/nova/volumes
enabled_apis=ec2,osapi_compute,metadata

network_api_class=nova.network.neutronv2.api.API
neutron_url=http://192.168.82.11:9696
neutron_auth_strategy=keystone
neutron_admin_tenant_name=service
neutron_admin_username=neutron
neutron_admin_password=service_pass
neutron_admin_auth_url=http://192.168.82.11:35357/v2.0
linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
security_group_api=neutron

compute_driver=libvirt.LibvirtDriver

instance_usage_audit=True
instance_usage_audit_period=hour
notify_on_state_change=vm_and_task_state
notification_driver=nova.openstack.common.notifier.rpc_notifier
notification_driver=ceilometer.compute.nova_notifier

#Metadata
service_neutron_metadata_proxy = True
neutron_metadata_proxy_shared_secret = helloOpenStack
#metadata_host=192.168.82.11
#metadata_listen=0.0.0.0
#enabled_apis=metadata


[database]
# The SQLAlchemy connection string used to connect to the database
connection = mysql://novaUser:novaPass@192.168.82.11/nova

And my /neutron/metadata_agent.ini file is,

[DEFAULT]
# Show debugging output in log (sets DEBUG log level output)
# debug = True

# The Neutron user information for accessing the Neutron API.
auth_url = http://192.168.82.11:35357/v2.0
admin_tenant_name = service
admin_user = neutron
admin_password = service_pass

# Network service endpoint type to pull from the keystone catalog
# endpoint_type = adminURL

# IP address used by Nova metadata server
nova_metadata_ip = 192.168.82.11

# TCP Port used by Nova metadata server
nova_metadata_port = 8775

# When proxying metadata requests, Neutron signs the Instance-ID header with a
# shared secret to prevent spoofing.  You may select any string for a secret,
# but it must match here and in the configuration used by the ...
(more)
edit retag flag offensive close merge delete

Comments

This might point you in the right direction, I also recommend just doing a search on the ask.openstack site for metadata issues, there should be quite a few amount of results that may help.

https://ask.openstack.org/en/question...

omar-munoz gravatar imageomar-munoz ( 2015-04-02 10:20:16 -0500 )edit