OOPS pruner should connect to a slave database
Bug #540084 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Stuart Bishop | ||
Bug Description
The OOPS pruner should connect to a slave database - it doesn't make any database changes so need not connect to the master at all.
Related branches
lp:~stub/launchpad/oops-pruning
- Gary Poster (community): Approve
-
Diff: 85 lines (+25/-12)2 files modifiedlib/canonical/launchpad/scripts/ftests/test_oops_prune.py (+9/-0)
lib/canonical/launchpad/scripts/oops.py (+16/-12)
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Stuart Bishop (stub) |
| milestone: | none → 10.03 |
| Changed in launchpad-foundations: | |
| status: | Triaged → In Progress |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #1 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in stable r10553 <http://