Ocata:EndpointNotFound: Could not find requested endpoint in Service Catalog. [closed]

asked 2017-05-23 09:45:15 -0500

zuoziqi gravatar image

updated 2017-05-23 10:49:13 -0500

I follow the offical document to install openstack Ocata on CentOS7, all verification has been succeed, but I cannot create instance via CLI or WebUI. Server log (nova-compute.log) show "EndpointNotFound: Could not find requested endpoint in Service Catalog" Error. Could ANYBODY can help me. Is this a bug?

Log Below:

4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Attempting claim: memory 1500 MB, disk 35 GB, vcpus 1 CPU
2017-05-23 12:08:49.393 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Total memory: 16382 MB, used: 512.00 MB
2017-05-23 12:08:49.394 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] memory limit: 24573.00 MB, free: 24061.00 MB
2017-05-23 12:08:49.394 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Total disk: 449 GB, used: 0.00 GB
2017-05-23 12:08:49.394 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] disk limit: 449.00 GB, free: 449.00 GB
2017-05-23 12:08:49.395 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Total vcpu: 4 VCPU, used: 0.00 VCPU
2017-05-23 12:08:49.395 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] vcpu limit not specified, defaulting to unlimited
2017-05-23 12:08:49.396 12353 INFO nova.compute.claims [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Claim successful
2017-05-23 12:08:49.804 12353 INFO nova.scheduler.client.report [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Submitted allocation for instance
2017-05-23 12:08:50.635 12353 WARNING nova.virt.osinfo [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2017-05-23 12:08:50.709 12353 WARNING nova.virt.osinfo [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2017-05-23 12:08:51.249 12353 INFO nova.compute.resource_tracker [req-372bdcaf-e95a-4c10-a7e5-758ce73c4993 - - - - -] Final resource view: name=main phys_ram=16382MB used_ram=2012MB phys_disk=449GB used_disk=35GB total_vcpus=4 used_vcpus=1 pci_stats=[]
2017-05-23 12:08:51.605 12353 WARNING nova.virt.osinfo [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] Cannot find OS information - Reason: (No configuration information found for operating system Empty)
2017-05-23 12:08:51.606 12353 INFO nova.virt.libvirt.driver [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] [instance: 89cda4c3-c3c3-49bc-b1fc-5382ea515c80] Creating image
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager [req-64eef975-4d76-4bba-afc2-7c57a1dca3e1 b85bc5aa14ab4392b099c57340f3f12a 4561eebad5994bb39e1299c36872ca52 - - -] Instance failed network setup after 1 attempt(s)
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager Traceback (most recent call last):
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1399, in _allocate_network_async
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager     bind_host_id=bind_host_id)
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 873, in allocate_for_instance
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager     bind_host_id, dhcp_options, available_macs)
2017-05-23 12:08:53.465 12353 ERROR nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 992, in ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Antonio G.
close date 2017-06-05 10:22:11.784577

Comments

My guess: auth_uri or auth_url in one of the config files on the compute node is incorrect.

Bernd Bausch gravatar imageBernd Bausch ( 2017-05-23 16:49:15 -0500 )edit

I recheck all the auth_url in nova.conf and make sure all auth_url has been set to http://controller:35357/ , but it still cannot work after I restart all Nova Service

zuoziqi gravatar imagezuoziqi ( 2017-05-23 20:01:58 -0500 )edit

Can you enable debug logging on the compute node? Then cause the error again and check if the log contains details about the endpoint that could not be found.

Bernd Bausch gravatar imageBernd Bausch ( 2017-05-24 02:04:01 -0500 )edit

Seem that problem has been solved, for there is a URL mistake which should be "http://" but it actually is "http:/"

zuoziqi gravatar imagezuoziqi ( 2017-05-24 02:50:21 -0500 )edit

Great that you found the typo.

Bernd Bausch gravatar imageBernd Bausch ( 2017-05-24 05:31:37 -0500 )edit