Subscription patching to duplicate in Redis should return 409 response
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
Fix Released
|
High
|
wangxiyuan |
Bug Description
Now, when use redis as the storage backend, if users update a subscription in a queue. It doesn't check the legality of the new
subscriber and doesn't update the subscriber section in redis as well.
Reproduce:
1. use redis backend and ensure there is a queue (we can name it test-queue)already.
2. create a subscription :
{
'subscriber': 'http://
'ttl': '3600',
'options': {}
}
3. create an other subscription:
{
'subscriber': 'http://
'ttl': '3600',
'options': {}
}
4. update the second subscription:
{
'subscriber': 'http://
}
expect: we can't update it because the subscriber is used by the first subscription.
actual: it's updated successfully.
and an other bug:
in step 4, we update the subscription:
{
'subscriber': 'http://
}
5. create the third subscription:
{
'subscriber': 'http://
}
expect: the third subscription should be created. because the 8001 does not be used
actual: it cant' be created.
6. create the forth subscription:
{
'subscriber': 'http://
}
expect: the forth subscription should not be created. because the 8002 is used by the second subscription
actual: it is created successfully.
Changed in zaqar: | |
assignee: | nobody → wangxiyuan (wangxiyuan) |
Changed in zaqar: | |
status: | New → In Progress |
Changed in zaqar: | |
importance: | Undecided → High |
milestone: | none → mitaka-rc1 |
tags: | added: release-critical |
summary: |
- The subscriber should be unique in redis backend. + Subscription patching to duplicate should return 409 response |
description: | updated |
description: | updated |
summary: |
- Subscription patching to duplicate should return 409 response + Subscription patching to duplicate in Redis should return 409 response |
https:/ /review. openstack. org/#/c/ 279946/