| 2016-01-16 04:08:45 |
Eva Balycheva |
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. |
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://ask.openstack.org/en/question/86758/zaqar-clicurl-issue/?answer=87333#post-id-87333 |
|
