Hey Tom. It's possible the code causing this bug was recently completely replaced when the SDK switched to using keystoneauth.
Can you please try this again with version 0.7.1 and see if the situation has improved?
Hey Tom. It's possible the code causing this bug was recently completely replaced when the SDK switched to using keystoneauth.
Can you please try this again with version 0.7.1 and see if the situation has improved?