new-slave.py no longer works

Bug #461800 reported by Stuart Bishop on 2009-10-27
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
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

Stuart Bishop (stub) on 2009-10-27
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Stuart Bishop (stub)
milestone: none → 3.1.10
Stuart Bishop (stub) on 2009-10-29
Changed in launchpad-foundations:
status: Triaged → In Progress
Ursula Junque (ursinha) on 2009-11-02
tags: added: current-rollout-blocker
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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers