Hi Josh, I found the problem, nova-compute tries to connect to the publicurl (xxx.xxx.240.10) of the keytone endpoints, this ip is not reachable from the management network. I thought the internalurl is the one, which is used for the internal communication of the openstack components and the publicurl is the ip for "customer" of the cluster? Am I wrong here? -martin On 30.05.2013 22:22, Martin Mailand wrote: > Hi Josh, > > On 30.05.2013 21:17, Josh Durgin wrote: >> It's trying to talk to the cinder api, and failing to connect at all. >> Perhaps there's a firewall preventing that on the compute host, or >> it's trying to use the wrong endpoint for cinder (check the keystone >> service and endpoint tables for the volume service). > > the keystone endpoint looks like this: > > | dd21ed74a9ac4744b2ea498609f0a86e | RegionOne | > http://xxx.xxx.240.10:8776/v1/$(tenant_id)s | > http://192.168.192.2:8776/v1/$(tenant_id)s | > http://192.168.192.2:8776/v1/$(tenant_id)s | > 5ad684c5a0154c13b54283b01744181b > > where 192.168.192.2 is the IP from the controller node. > > And from the compute node a telnet 192.168.192.2 8776 is working. > > -martin > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |