Re: [Rdo-list] tempest_config fails if network service is not enabled

Correct - just found out that Neutron is installed, for some reason, but fails to connect to the AMQP server for some unknown reason. Investigating... Y. From: David Kranz [mailto:dkranz@redhat.com] Sent: Thursday, January 08, 2015 4:04 PM To: Kaul, Yaniv; rdo-list(a)redhat.com Subject: Re: [Rdo-list] tempest_config fails if network service is not enabled On 01/08/2015 07:12 AM, Kaul, Yaniv wrote: Not everyone needs network for testing... [root@lgdrm1499 tempest(keystone_admin)]# tools/config_tempest.py --create identity.uri $OS_AUTH_URL identity.admin_username $OS_USERNAME identity.admin_password $OS_PASSWORD identity.admin_tenant_name $OS_TENANT_NAME 2015-01-08 14:10:41,932 - tempest.common.api_discovery - ERROR - Request on service 'network' with url 'http://10.102.37.163:9696/v2.0/extensions.json' failed Traceback (most recent call last): File "tools/config_tempest.py", line 782, in <module> main() File "tools/config_tempest.py", line 137, in main services = api_discovery.discover(clients.identity) File "/root/tempest/tempest/common/api_discovery.py", line 143, in discover services[name]['extensions'] = service.get_extensions() File "/root/tempest/tempest/common/api_discovery.py", line 83, in get_extensions body = self.do_get(self.service_url + 'v2.0/extensions.json') File "/root/tempest/tempest/common/api_discovery.py", line 47, in do_get raise e socket.error: [Errno 111] Connection refused (I believe it used to work in the past, so it's most likely a regression). The discovery is done for each service listed in the keystone catalog. Is it possible that your catalog lists a neutron endpoint but neutron was not configured or its port is blocked? -David TIA, Y. _______________________________________________ Rdo-list mailing list Rdo-list@redhat.com<mailto:Rdo-list@redhat.com> https://www.redhat.com/mailman/listinfo/rdo-list