Hi All, My instances are timing out while obtaining their meta-data. They are being spawned on the same controller node in which I am running nova-network and nova-api services. The networks are being provisioned through the Quantum V2 API. I have enabled meta-data in my nova.conf. Any thoughts on how to resolve this issue?. Thanks /
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 1.27. request failed wget: can't connect to remote host (169.254.169.254): Connection timed out cloud-setup: failed 2/30: up 191.69. request failed wget: can't connect to remote host (169.254.169.254): Connection timed out cloud-setup: failed 3/30: up 382.15. request failed wget: can't connect to remote host (169.254.169.254): Connection timed out cloud-setup: failed 4/30: up 572.61. request failed wget: can't connect to remote host (169.254.169.254): Connection timed out cloud-setup: failed 5/30: up 763.08. request failed wget: can't connect to remote host (169.254.169.254): Connection timed out cloud-setup: failed 6/30: up 953.54. request failed sudo grep -i metadata /etc/nova/nova.conf enabled_apis=ec2,osapi_compute,osapi_volume,metadata metadata_host=$my_ip #### (StrOpt) the ip for the metadata api server metadata_port=8775 #### (IntOpt) the port for the metadata api port # quota_metadata_items=128 #### (IntOpt) number of metadata items allowed per instance metadata_manager=nova.api.manager.MetadataManager #### (StrOpt) OpenStack metadata service manager metadata_listen=0.0.0.0 #### (StrOpt) IP address for metadata api to listen metadata_listen_port=8775 #### (IntOpt) port for metadata api to listen # metadata_workers=0 #### (IntOpt) Number of workers for metadata API
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
