tripleo

tripleoclient shouldn't delete the tripeo queue

Bug #1757984 reported by Dougal Matthews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Dougal Matthews
tripleo rocky-1

Bug Description

In queens tripleoclient started to use the default queue for workflow messages. Previously it used a queue with a UUID name, it then deleted the queue when it was finished. Deleting the queue no longer makes sense when it is a known queue we want to keep.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tripleoclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/555193

Changed in tripleo:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tripleoclient (master)

Reviewed: https://review.openstack.org/555193
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=99520c98b81e335bff915017d99355083daf13c9
Submitter: Zuul
Branch: master

commit 99520c98b81e335bff915017d99355083daf13c9
Author: Dougal Matthews <email address hidden>
Date: Thu Mar 22 08:35:42 2018 +0000

    Don't delete the tripleo Zaqar queue

    Now that we share a queue with other commands and other clients (the GUI
    at least) we should never delete the queue.

    Closes-Bug: #1757984
    Change-Id: I1555b5e43984dea941885f221c4ec46092a34735

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 10.0.0

This issue was fixed in the openstack/python-tripleoclient 10.0.0 release.

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

Other bug subscribers

Remote bug watches

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