Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cloud Networks client timing issue #406

Closed
rs-randallburt opened this issue Jun 18, 2014 · 1 comment
Closed

Cloud Networks client timing issue #406

rs-randallburt opened this issue Jun 18, 2014 · 1 comment
Labels

Comments

@rs-randallburt
Copy link
Contributor

1.8.2 added a fix that allowed for special handling of the Cloud Networks client and service type. However, if I use a pyrax context and first grab the client for "compute", the context will return the nova client if I then ask for the client for "networks" because the caching doesn't take client_class into account if its passed. I didn't test, but I assume the reverse is true (if I ask for the "networks" client first, I'll get that if I subsequently ask for the "compute" client).

@EdLeafe EdLeafe added the bug label Jun 18, 2014
@EdLeafe
Copy link
Contributor

EdLeafe commented Jun 18, 2014

Confirmed. I'll get a fix out shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants