Launchpad itself

staging not updating, apparently because of slony error

Bug #527333 reported by Gary Poster
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Medium
Stuart Bishop

Bug Description

Pastebin: https://pastebin.canonical.com/28318/

Affecting QA for entire team, so critical.

Revision history for this message
Stuart Bishop (stub) wrote :

Looks like a race condition - we haven't tripped over it before. Trying to do a slony operation while slony is still busy in the background.

summary: - staging is down, apparently because of slony error
+ staging not updating, apparently because of slony error
Changed in launchpad-foundations:
importance: Critical → Medium
Revision history for this message
Stuart Bishop (stub) wrote :

If we see this again, we need to insert some sleeps. Or upgrade Slony-I. We can't block until replication has settled down, because the failing component is the script that blocks until replication has settled down.

Changed in launchpad-foundations:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.