Comment 4 for bug 1893214

It looks like this occurs when getting a token for a user that doesn't have a default project set, and only when using the get_keystone_token function to obtain a token.

Updating the get_keystone_token function to use the json from the bug description looks like it would be a complete and proper fix to me.

> Is there some configuration that needs to be tested before committing a patch with the updated json?, otherwise I can propose a patch.

Not that I'm aware of. A patch would be much appreciated!