Matt Martz

I've confirmed this fixes my issue. Instead of: ``` 422 {"message":"Validation Failed","errors":[{"resource":"Issue","code":"missing_field","field":"title"}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} ``` The PR is properly created.

> Any ETA on merging this? Thanks! No, the PR uses incorrect defaults and assumptions.

novaclient 2.21.0 deprecated the v1.1 client, and is issuing that warning. In novaclient 2.21.0, the v1.1 client is now an alias to the v2 client. We will need to test...

I've started some investigation into what would be required to prevent the warning. One of the `rackspace-novaclient` dependencies will still cause the warning regardless of the changes made in pyrax....

I'm not sure that this is the correct approach. Since pyrax can work within contexts, I think that a session would need to be created for the individual contexts, rather...

Looks like based on the discussion, that additional information needs to be added to the documentation stating that the `tenant_id` is required for RBAC users.

The problem is not with pyrax, but 2 modules that `rackspace-novaclient` is dependent on: 1. os-networksv2-python-novaclient-ext 2. os-virtual-interfacesv2-python-novaclient-ext Removing those packages for now should resolve the issue: ``` pip uninstall...

See: 1. https://github.com/rackerlabs/os_networksv2_python_novaclient_ext/pull/4 2. https://github.com/Cerberus98/os_virtual_interfacesv2_ext/pull/3

Just as another option, downgrading to an older version of python-novaclient such as 2.20.0 should also resolve the issue.

Ok, it appears as though new versions of the affected extensions were just pushed to pypi. `pip install -U os-networksv2-python-novaclient-ext==0.24 os-virtual-interfacesv2-python-novaclient-ext==0.18 python-novaclient==2.21.0` Please let me know if this is resolving...