new-slave.py no longer works
Bug #461800 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Stuart Bishop | ||
Bug Description
One of the first steps new-slave.py does is duplicate the schema of the master database. Unfortunately, this no longer works as we now have two master databases (the authdb replication set master and the lpmain replication set master). new-slave.py needs to be fixed to cope.
Related branches
lp://staging/~stub/launchpad/replication
- Abel Deuring (community): Approve (code)
- Aaron Bentley (community): Approve
-
Diff: 196 lines (+106/-19)7 files modifieddaemons/cache-database-replication-lag.py (+53/-0)
database/replication/helpers.py (+1/-0)
database/schema/comments.sql (+4/-0)
database/schema/patch-2207-28-1.sql (+9/-0)
database/schema/security.cfg (+6/-0)
database/schema/trusted.sql (+22/-0)
lib/canonical/launchpad/webapp/dbpolicy.py (+11/-19)
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Stuart Bishop (stub) |
| milestone: | none → 3.1.10 |
| Changed in launchpad-foundations: | |
| status: | Triaged → In Progress |
| tags: | added: current-rollout-blocker |
Revision history for this message
| Diogo Matsubara (matsubara) wrote Bug fixed by a commit | #1 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in devel r9830 <http://