Hrm, good catch! I see no problems with that request at all...
-Dolph Mathews
On May 9, 2012, at 5:58 PM, "Kevin L. Mitchell" <kevin.mitch...@rackspace.com>
wrote:
> On Wed, 2012-05-09 at 15:32 -0500, Dolph Mathews wrote:
>> It also just occurred to me that perhaps you're using a *very* old
>> novaclient against a more recent version of keystone?
>
> Actually, if you look a little more closely:
>
>> $ nova --debug image-list
>> connect: (192.168.1.71, 5000)
>> send: 'POST /v2.0/tokens HTTP/1.1\r\nHost:
>> 192.168.1.71:5000\r\nContent-Length: 117\r
>> \ncontent-type:
>> application/json\r\naccept-encoding: gzip, deflate\r
>> \naccept:
>> application/json\r\nuser-agent: python-novaclient\r\n
>> \r\n{"auth":
> ^^^^^^^^
>> {"tenantName": "labSpaceDemo", "passwordCredentials":
>> {"username":
>> "adminUser", "password": "lfplhfgthvf"}}}'
>
> The request body for Keystone is not, in fact, malformed. It would be
> interesting to look at the nova-api logs for this request…
> --
> Kevin L. Mitchell <kevin.mitch...@rackspace.com>
>
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
