32950 - Bugzilla DUPL messages appears on DUP-to bug, but not on DUP-of bug

Status: VERIFIED DUPLICATE of bug 7873

(Bugzilla :: Bugzilla-General, defect, P3)

Description

[John Morrison]

This is the second time I have seen this occur in the past two days.

Basically, someone decides that Bug B is a duplicate of Bug A and (I assume)
marks it as such.

What happens is that the annotation  "*** Bug B has been marked as a duplicate 
of this bug. ***" appears on Bug A, but Bug B is *not* placed into the DUPL
state (and no message is placed on that bug). 

Examples: 
         Bug A              Bug B
3/21     bug #30878         bug #20020
3/22     bug #26508         bug #32827

I suppose this may have to do with the shadow db, but note that the 
annotation to bug #20020 never arrived. (Eric closed it as a DUPL
a second time today, and that one worked).

Comment 1

[Jesse Ruderman]

From bug 33718:

"Whoops...  it looks like it let me do that before I'm logged in, but didn't
actually resolve the bug.  Someone mark 33719 and 33720 as dups of this bug."

Comment 2

[Jesse Ruderman]

Mid-air collisions can also cause this.  Bug 7873.

Comment 3

[Terry Weissman]

[e-mail] is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

Comment 4

[Sean Richardson]

See also bug 32871, "Lost DUP resolution for Mozilla bugs 32805, 32820, 
20020..." -- the essential problem here seems to be that the message is added
to the DUP-to-bug before anything else, including checking for permissions,
logged-in status, and mid-air collisions. The prime evidence, other than seeing
those messages sometimes without a corresponding message in the bug that
should have been resolved, is that on the "Processing" page, the DUP-to-bug
is the first processed. If this is what is happening, the only real solution is 
to stop doing that. 

Shall we move all this to bug 7873, "mid air collision and duplicates"?

Comment 5

[Sean Richardson]

*** Bug 28673 has been marked as a duplicate of this bug. ***

Comment 6

[Dave Miller [:justdave]]

I'll confirm this is the same problem (although not exactly the same symptoms) as 
bug 7873.  When 7873 is fixed, this one will be.


*** This bug has been marked as a duplicate of 7873 ***

Comment 7

[Sean Richardson]

Verfying; the specific issues mentioned here are now part of bug 7873,
resummarized as "duplicate isn't always resolved DUP when marking as such".

Comment 8

[Dave Miller [:justdave]]

moving all closed Bugzilla bugs to the new Bugzilla product.
This batch is DUPLICATE/INVALID/WORKSFORME/WONTFIX
reassigning to default owner and QA in case of the bug being reopened.
Clearing milestones, since we really shouldn't have them on these types of
resolutions.  Sorry for the spam everyone...

Comment 9

[Markus Gerstel]

Verification got lost