Zaqar can't list queues, when enable_virtual_pool = True (affects devstack)
Bug #1533668 reported by
Eva Balycheva
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
Fix Released
|
High
|
Thomas Herve |
Bug Description
This bug also affects DevStack's Zaqar installation.
When in zaqar.conf:
[DEFAULT]
pooling = True
[pooling:catalog]
enable_virtual_pool = True
It's possible to create a queue using openstack client or curl request. I can see created queues in Zaqar's database.
But when Zaqar is asked to list queues, Zaqar always responds with 200 OK http response with body:
{"queues": [], "links": []}
The list of queues is always empty, even if there's a queue in Zaqar's database.
Once I turn off these two options, Zaqar list queues normally.
Update: a user is experiencing this problem: https:/
description: | updated |
Changed in zaqar: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in zaqar: | |
assignee: | nobody → Thomas Herve (therve) |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/269165 /git.openstack. org/cgit/ openstack/ zaqar/commit/ ?id=460ecce2ecf e3e70adf9b0721a 6a7bce2ffd2832
Committed: https:/
Submitter: Jenkins
Branch: master
commit 460ecce2ecfe3e7 0adf9b0721a6a7b ce2ffd2832
Author: Thomas Herve <email address hidden>
Date: Mon Jan 18 17:08:19 2016 +0100
Use default pool for queue listing
While we're properly use a default pool when manipulating a specific
queue, we don't use it when actually listing queues. This fixes it by
using the same mechanism.
Change-Id: Ie2329389bf9279 3af0c8d7a676fca da757fd26d7
Closes-Bug: #1533668