Zaqar can't list queues, when enable_virtual_pool = True (affects devstack)

Bug #1533668 reported by Eva Balycheva
6
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://ask.openstack.org/en/question/86758/zaqar-clicurl-issue/?answer=87333#post-id-87333

Eva Balycheva (ubershy)
description: updated
Feilong Wang (flwang)
Changed in zaqar:
status: New → Triaged
importance: Undecided → High
Thomas Herve (therve)
Changed in zaqar:
assignee: nobody → Thomas Herve (therve)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zaqar (master)

Reviewed: https://review.openstack.org/269165
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=460ecce2ecfe3e70adf9b0721a6a7bce2ffd2832
Submitter: Jenkins
Branch: master

commit 460ecce2ecfe3e70adf9b0721a6a7bce2ffd2832
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: Ie2329389bf92793af0c8d7a676fcada757fd26d7
    Closes-Bug: #1533668

Changed in zaqar:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/zaqar 2.0.0.0b3

This issue was fixed in the openstack/zaqar 2.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.