Celery does not use specified virtual host
Bug #973463 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Aaron Bentley | ||
Bug Description
Asuka distinguishes between staging and qastaging rabbitmq by virtual host, but Launchpad's celery config does not take this into account. This means that tasks intended for qastaging will be mixed with tasks intended for staging.
Related branches
lp:~abentley/launchpad/celery-rabbit-config
- Abel Deuring (community): Approve (code)
-
Diff: 33 lines (+10/-2)2 files modifiedlib/lp/services/job/celeryconfig.py (+6/-1)
lib/lp/services/job/tests/__init__.py (+4/-1)
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → Aaron Bentley (abentley) |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | Triaged → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r15066 <http://