<div dir="ltr">Hi guys now i'm dealing with a problem between horizon and my quantum api. When i click into de networks in horizon i get "<strong>Error: </strong>Network list can not be retrieved." so i checked the dashboard error.log file and this is what i've:<div>
<br></div><div><div>[Mon May 06 19:51:17 2013] [error] \x1b[31;1mRecoverable error: [Errno 111] Connection refused\x1b[0m</div><div>[Mon May 06 19:51:18 2013] [error] \x1b[31;1mRecoverable error: [Errno 111] Connection refused\x1b[0m</div>
<div><br></div><div style>I assumed this message means that it's not possible to reach quantum-server so i used the console client:</div><div style><br></div><div style> root@locro:~# quantum --os-username=admin --os-tenant-name=admin --os-password=XXX --os-auth-url=<a href="http://172.19.136.1:35357/v2.0">http://172.19.136.1:35357/v2.0</a> net-list</div>
<div>+--------------------------------------+-------+-----------------------------------------------------+</div><div>| id                                   | name  | subnets                                             |</div>
<div>+--------------------------------------+-------+-----------------------------------------------------+</div><div>| 94fb127a-03e4-41a1-b397-8eefd2ede11b | vlan1 | cb5bbc6f-a380-4abd-8e85-b55e977adc0f <a href="http://172.16.16.0/24">172.16.16.0/24</a> |</div>
<div>+--------------------------------------+-------+-----------------------------------------------------+</div><div>root@locro:~# </div><div><br></div><div style>It works just great, but what's the problem then? I checked my endpoints and services:</div>
<div style><br></div><div style><div><div>root@locro:~# keystone --os-username=admin --os-tenant-name=admin --os-password=XXX --os-auth-url=<a href="http://172.19.136.1:35357/v2.0">http://172.19.136.1:35357/v2.0</a> endpoint-list</div>
<div>+----------------------------------+-----------+-------------------------------------------------+-------------------------------------------------+---------------------------------------------+----------------------------------+</div>
<div>|                id                |   region  |                    publicurl                    |                   internalurl                   |                   adminurl                  |            service_id            |</div>
<div>+----------------------------------+-----------+-------------------------------------------------+-------------------------------------------------+---------------------------------------------+----------------------------------+</div>
<div>...</div><div>| 11c4108e48e34e0a9924f1266ab657ea | RegionOne |            <a href="http://172.19.136.1:9696/">http://172.19.136.1:9696/</a>            |            <a href="http://172.19.136.1:9696/">http://172.19.136.1:9696/</a>            |          <a href="http://172.19.136.1:9696/">http://172.19.136.1:9696/</a>          | 5899ffd62e994f929f0980d56391a84b |</div>
<div>...</div><div>+----------------------------------+-----------+-------------------------------------------------+-------------------------------------------------+---------------------------------------------+----------------------------------+</div>
<div>root@locro:~# keystone --os-username=admin --os-tenant-name=admin --os-password=XXX --os-auth-url=<a href="http://172.19.136.1:35357/v2.0">http://172.19.136.1:35357/v2.0</a> service-list</div><div>+----------------------------------+----------+--------------+------------------------------+</div>
<div>|                id                |   name   |     type     |         description          |</div><div>+----------------------------------+----------+--------------+------------------------------+</div><div>...</div>
<div>| 5899ffd62e994f929f0980d56391a84b | quantum  |   network    | OpenStack Networking service |</div><div>...</div><div>+----------------------------------+----------+--------------+------------------------------+</div>
</div><div><br></div><div style>Everything looked ok. I thought that maybe... horinzon could be trying to reach quantum-server on the same host that it's running, so...:</div><div style><br></div><div style><div>root@locro:~# nc -l 172.19.136.11 9696</div>
<div>GET //v2.0/networks.json?shared=False&tenant_id=d1a1563eb7604307bc385817ab0adccf HTTP/1.1</div><div>Host: <a href="http://172.19.136.11:9696">172.19.136.11:9696</a></div><div>x-auth-token: 67a61c861b0542f1bd52021d0e39d5e1</div>
<div>content-type: application/json</div><div>accept-encoding: gzip, deflate</div><div>accept: application/json</div><div>user-agent: python-quantumclient</div><div><br></div></div><div style>Indeed it is. But... Why? It should take the quantum endpoint from keystone, shouldn't it? Somehow horizon is not using keystone endpoints to get the quantum server IP, is this correct? Is there a way i can tell horizon where my quantum-api is??? Thanks guys!!! </div>
</div>-- <br>Pavlik Juan José
</div></div>