zaqar

Failed to handle queue actions for pooling

Bug #1679888 reported by Feilong Wang on 2017-04-05

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	zaqar	Fix Released	Critical	Feilong Wang

Bug Description

Now we're putting queues in control plane so it's not necessary to look for pools when doing queues actions.

Feilong Wang (flwang) on 2017-04-05

Changed in zaqar:
assignee:	nobody → Fei Long Wang (flwang)
importance:	Undecided → High

OpenStack Infra (hudson-openstack) on 2017-04-07

Changed in zaqar:
status:	New → In Progress

Feilong Wang (flwang) on 2017-04-11

Changed in zaqar:
importance:	High → Critical

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2017-04-28: Fix merged to zaqar (master)

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

commit fe4f1e59aef60c43ae97fb8172b840d3b7ef066a
Author: Fei Long Wang <email address hidden>
Date: Wed Apr 5 14:57:50 2017 +1200

Fix queues actions for pooling

    Based on current design, Zaqar is storing queues in management database
    instead of message database. As a result, it's not necessary now to look
    up pools to get the correct queue controller. This patch fixes the pooling
    issue and the test.

Closes-Bug: #1679888

Depends-On: I5195911d22d5935aa3de105fe735ac159276a025

Co-Authored-By: wangxiyuan<email address hidden>
Change-Id: Ie20e0c611dc0756818e4612f33ebc2ab2ecd2990