TypeError on unicode token with some openstack setups

[Patrick Hetu]

Using the lastest trunk (561) I had this error in the bootstrap with the openstack provider:

flocon:~$ juju -v bootstrap
2012-07-30 10:30:19,806 DEBUG Initializing juju bootstrap runtime
2012-07-30 10:30:19,815 DEBUG openstack: using auth-mode 'userpass' with http://avoine.dyndns.info:5000/v2.0/
2012-07-30 10:30:20,133 DEBUG openstack: authenticated til u'2012-07-31T14:30:35Z'
2012-07-30 10:30:20,134 DEBUG openstack: GET 'http://avoine.dyndns.info:8774/v1.1/78c586f85d3c411f8a5d402f682e00e7/flavors'
Traceback (most recent call last):
Failure: twisted.web._newclient.RequestGenerationFailed: [<twisted.python.failure.Failure <type 'exceptions.TypeError'>>]
2012-07-30 10:30:20,136 ERROR Traceback (most recent call last):
Failure: twisted.web._newclient.RequestGenerationFailed: [<twisted.python.failure.Failure <type 'exceptions.TypeError'>>]

2012-07-30 10:30:20,136 ERROR [<twisted.python.failure.Failure <type 'exceptions.TypeError'>>]

Turn out to be the token returned by keystone that was in UTF-8 and makes the next Request Generation to fail.
So if I force the str type in the token id recuperation in the _handle_v2_auth function the error go away.
But it surely have a better way to solve this.

[Martin Packman (gz)]

Thanks Patrick. That change is sufficient if the token does not in fact contain any non-ascii characters?

[Patrick Hetu (patrick-hetu)]

Well, I doesn't and according to keystone specs it never will.
Do you want a merge request?

[Martin Packman (gz)]

You'd confused me a little by saying UTF-8 in the original report. :)

I'll get to this as part of cleaning up the client code, but feel free to propose a merge now if you're happy doing that.