trove taskmanager_queue can not be changed
Bug #1462734 reported by
jazeltq
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Medium
|
jazeltq |
Bug Description
In the trove.taskmanag
we defined the target like this
target = messaging.
But in the setupt of taskmanager, we defined like this:
@with_
def main(conf):
startup(conf, None)
Then the topic can not be sent in. So we can not change the option CONF.taskmanage
If we change it in configuration file, the taskmanager can not get any message because it still declare on the default consumer queue.
Changed in trove: | |
assignee: | nobody → jazeltq (jazeltq-k) |
Changed in trove: | |
status: | New → In Progress |
Changed in trove: | |
milestone: | none → liberty-1 |
importance: | Undecided → Medium |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | liberty-1 → 4.0.0 |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 189093/