Launchpad itself

Package copy attempting to write to a slave object.

Bug #367190 reported by Scott Evans
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

Whilst attempting to copy a recently built package from Me TV development back to my ppa "intrepid" I get the following (Error ID: OOPS-1212EA687) and I only have the option to return back to the main entry of launchpad.

This also occurs if I'm attempting to copy from my ppa "Jaunty" to "intrepid" as well. But on each attempt I got a different OOPS reference!

There are other OOPSes with the same type of failure for other views and tables.

 InternalError: Slony-I: Table securesourcepackagepublishinghistory is replicated and cannot be modified on a subscriber node

See original description
Tags: lp-soyuz oops
Revision history for this message
William Grant (wgrant) wrote :

This is a general problem - the main slave store is being selected instead of the main master store, on lots of edge writes.

affects: soyuz → launchpad-foundations
Changed in launchpad-foundations:
status: New → Confirmed
summary: - Error copying packages from one ppa to another (Error ID:
- OOPS-1212EA687)
+ Slave store being inappropriately chosen for writes
description: updated
Diogo Matsubara (matsubara)
description: updated
tags: added: oops
Revision history for this message
Stuart Bishop (stub) wrote : Re: Slave store being inappropriately chosen for writes

It looks like some IMasterObject(obj) casts are needed to ensure we are working with a writable object.

affects: launchpad-foundations → soyuz
Changed in soyuz:
status: Confirmed → Triaged
summary: - Slave store being inappropriately chosen for writes
+ Package copy attempting to write to a slave object.
Revision history for this message
Stuart Bishop (stub) wrote :

I'm not sure if this is still happening.

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

I don't think anyone can look at this without a more recent traceback.

Changed in soyuz:
status: Triaged → Incomplete
Revision history for this message
William Grant (wgrant) wrote :

It's not a Soyuz bug. This was happening throughout Launchpad when this bug was filed, although somebody fixed it later that day and I haven't seen it since.

Revision history for this message
Savvas Radevic (medigeek) wrote :

That's true, at least I can't confirm it anymore

Revision history for this message
Scott Evans (vk7hse) wrote :

I've not had this issue since so I suppose this can be written off? (Invalid)

Changed in soyuz:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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