Launchpad itself

Changing bug project fails when milestone set

Bug #384309 reported by Paul Sladen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

This is a guess at the cause of this oops, so the Summary may need changing. If I go to the bug:

  https://bugs.launchpad.net/ubuntuone-client/+bug/377346

and try to change the Project to 'ubunet' it responds with:

  (Error ID: OOPS-1253F1019)

My presumption is that this is related to the presence of a project-specific milestone; however /that/ bug was claimed to be fixed by bug #6026 in 2006, so it maybe something else.

Regardless, trying to make the change failed.

Tags: lp-bugs oops
Revision history for this message
Eleanor Berger (intellectronica) wrote :

The milestone isn't being cleared and when trying to update a database constraint is triggered. The fix is to clear the milestone when the bug target changes.

Changed in malone:
importance: Undecided → High
milestone: none → 2.2.6
status: New → Triaged
Revision history for this message
Eleanor Berger (intellectronica) wrote :

As a workaround, until this bug is fixed, clear the milestone in the bug you want to re-target manually, before changing the project.

Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 384309] Re: Changing project fails if milestone is set

On Sat, Jun 06, 2009 at 05:10:24PM -0000, Tom Berger wrote:
> The milestone isn't being cleared and when trying to update a database
> constraint is triggered. The fix is to clear the milestone when the bug
> target changes.

We do clear the milestone automatically. Sometimes, though, this bug is
triggered. This is the first time I've seen this bug triggered for about
a year now. I think we have a bug reported about this.

I suspect that there is a race condition when the actual SQL commands
are sent, causing the target column to be changed before the milestone
is cleared.

Revision history for this message
Paul Sladen (sladen) wrote : Re: Changing project fails if milestone is set

IIRC, I hit it on four-separate bugs last night (all ubunet/ubuntuone-* related).

Is there something special in this case? Are there any "private" settings in use on either of those projects which would trigger it?

Eleanor Berger (intellectronica)
Changed in malone:
assignee: nobody → Tom Berger (intellectronica)
status: Triaged → In Progress
Eleanor Berger (intellectronica)
Changed in malone:
assignee: Tom Berger (intellectronica) → nobody
milestone: 2.2.6 → 2.2.7
status: In Progress → Triaged
Eleanor Berger (intellectronica)
Changed in malone:
milestone: 2.2.7 → 2.2.8
Deryck Hodge (deryck)
Changed in malone:
milestone: 2.2.8 → none
Robert Collins (lifeless)
tags: added: oops
summary: - Changing project fails if milestone is set
+ Changing bug project fails when milestone set
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.