<p>Well, instead of it I did use the real uuid of service tenant)) <br>
End, actually that clarify about %(tenant_id)s is exist at docs.</p>
<p>BTW, for what reason needs to execute TENANT variable in the volume section?</p>
<div class="gmail_quote">On May 13, 2012 5:55 PM, "Dolph Mathews" <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Igor,</div><div><br></div>What did you use instead / how did you interpret that portion of the docs?<div><br></div><div>I think we need to clarify in the docs that %(tenant_id)s is very intentional, and intended to be used exactly as written (and explain how it behaves) -- you're certainly not the first person to run into this kind of issue on endpoints.</div>
<div><br></div><div>-Dolph<br><br><div class="gmail_quote">On Sun, May 13, 2012 at 8:42 AM, Igor Laskovy <span dir="ltr"><<a href="mailto:igor.laskovy@gmail.com" target="_blank">igor.laskovy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<br>
<br>
I have solved this problem))<br>
For me it was incorrect built endpoints in keystone for nova and<br>
volume services.<br>
I thought that %(tenant_id)s is mistake as other mistakes in the<br>
installation guide<br>
(<a href="http://docs.openstack.org/trunk/openstack-compute/install/content/keystone-service-endpoint-create.html" target="_blank">http://docs.openstack.org/trunk/openstack-compute/install/content/keystone-service-endpoint-create.html</a>),<br>
but it wasn't .<br>
<br>
Thanks everybody for attention!<br>
<div><div><br>
On Sat, May 12, 2012 at 4:53 PM, Igor Laskovy <<a href="mailto:igor.laskovy@gmail.com" target="_blank">igor.laskovy@gmail.com</a>> wrote:<br>
> Guys, I am still need help))<br>
><br>
> On May 10, 2012 9:45 PM, "Igor Laskovy" <<a href="mailto:igor.laskovy@gmail.com" target="_blank">igor.laskovy@gmail.com</a>> wrote:<br>
>><br>
>> Hi Dolph and Kevin,<br>
>> thank you for your attention and sorry for delay reply.<br>
>><br>
>> Here are what I have in nova-api.log :<br>
>><br>
>> 2012-05-10 14:40:08 INFO nova.api.openstack.wsgi<br>
>> [req-c6b9ea76-bbe1-4796-a231-41fc41c7695f<br>
>> 50be127b9b7f49dcbf5ffea06d23d83a ebf29e67cbd445daa5ad09f76cdf69f9] GET<br>
>> <a href="http://192.168.1.71:8774/v2/7033300637bc4964a8d0a43649fcf898/images/detail" target="_blank">http://192.168.1.71:8774/v2/7033300637bc4964a8d0a43649fcf898/images/detail</a><br>
>><br>
>> 2012-05-10 14:40:08 DEBUG nova.api.openstack.wsgi<br>
>> [req-c6b9ea76-bbe1-4796-a231-41fc41c7695f<br>
>> 50be127b9b7f49dcbf5ffea06d23d83a ebf29e67cbd445daa5ad09f76cdf69f9]<br>
>> Unrecognized Content-Type provided in request from (pid=1005) get_body<br>
>> /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py:697<br>
>><br>
>> On Thu, May 10, 2012 at 2:27 AM, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com" target="_blank">dolph.mathews@gmail.com</a>><br>
>> wrote:<br>
>> > Hrm, good catch! I see no problems with that request at all...<br>
>> ><br>
>> > -Dolph Mathews<br>
>> ><br>
>> > On May 9, 2012, at 5:58 PM, "Kevin L. Mitchell"<br>
>> > <<a href="mailto:kevin.mitchell@rackspace.com" target="_blank">kevin.mitchell@rackspace.com</a>> wrote:<br>
>> ><br>
>> >> On Wed, 2012-05-09 at 15:32 -0500, Dolph Mathews wrote:<br>
>> >>> It also just occurred to me that perhaps you're using a *very* old<br>
>> >>> novaclient against a more recent version of keystone?<br>
>> >><br>
>> >> Actually, if you look a little more closely:<br>
>> >><br>
>> >>> $ nova --debug image-list<br>
>> >>> connect: (192.168.1.71, 5000)<br>
>> >>> send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:<br>
>> >>> <a href="http://192.168.1.71:5000" target="_blank">192.168.1.71:5000</a>\r\nContent-Length: 117\r<br>
>> >>> \ncontent-type:<br>
>> >>> application/json\r\naccept-encoding: gzip, deflate\r<br>
>> >>> \naccept:<br>
>> >>> application/json\r\nuser-agent: python-novaclient\r\n<br>
>> >>> \r\n{"auth":<br>
>> >> ^^^^^^^^<br>
>> >>> {"tenantName": "labSpaceDemo", "passwordCredentials":<br>
>> >>> {"username":<br>
>> >>> "adminUser", "password": "lfplhfgthvf"}}}'<br>
>> >><br>
>> >> The request body for Keystone is not, in fact, malformed. It would be<br>
>> >> interesting to look at the nova-api logs for this request…<br>
>> >> --<br>
>> >> Kevin L. Mitchell <<a href="mailto:kevin.mitchell@rackspace.com" target="_blank">kevin.mitchell@rackspace.com</a>><br>
>> >><br>
>><br>
>><br>
>><br>
>> --<br>
>> Igor Laskovy<br>
<br>
<br>
<br>
</div></div><span><font color="#888888">--<br>
Igor Laskovy<br>
</font></span></blockquote></div><br></div>
</blockquote></div>