Nova and Neutron client factories can return incorrect clients on second call
Bug #1543269 reported by
Adam Harwell
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
High
|
Unassigned |
Bug Description
Example of the nova client cacheing and ignoring any passed args:
If the first call to this class is a public client and the next is for an admin client, both will be public clients, causing the admin operations to fail (or the opposite).
Discussion can be found here: https:/
description: | updated |
tags: | added: lbaas |
Changed in octavia: | |
importance: | Undecided → High |
tags: | removed: lbaas |
tags: | added: target-mitaka |
tags: | removed: target-mitaka |
tags: | added: osic |
tags: | removed: osic |
To post a comment you must log in.
Hi Adam.
I can see from the description that this is a bug found during code review of the https:/ /review. openstack. org/#/c/ 271476/ patch. Do you intend to work on the fix?
Thanks,
Martin