Landings referencing a closed bug are seen as orphaned

[William Grant]

qa-tagger appears to only consider open bugs when looking at landings. Anything without an open bug is seen as orphaned and deployable.

This is less than ideal when we roll production back after closing bugs, as everything appears to be orphaned and bugs must be reopened before they can be retagged.

See also
========

Bug 494807 - we don't know which bugs are fixed by a landing, only by a branch as a whole. Without that fixed, we cannot tell which fixed bugs should need re-opening and re-tagging.

[Aaron Bentley (abentley)]

Marking critical because it can lead to qa being missed, and bad code being deployed.

[Robert Collins (lifeless)]

I don't think it can do that in any regular way? If we rollback prod because of an issue, we will reopen the bug for the revision that caused the rollback, so it will show correctly. The other revisions will show wonkily, and I agree its an issue there.

I assume I've missed a scenario :)

(Dropping to high pending the outcome of this discussion).

[Ursula Junque (ursinha)]

Considering only open bugs was a requested behavior, due to people
reusing branches then causing qatagger to bring all linked bugs, not
only the pertinent ones.

Possible solution is to create a script that marks the bugs as Fix
Released in a hourly basis or something, so we don't have to touch QA
tagger or the process, neither worry about timing closing/tagging
bugs.

On Sat, Aug 6, 2011 at 6:18 AM, Robert Collins
<email address hidden> wrote:
> I don't think it can do that in any regular way? If we rollback prod
> because of an issue, we will reopen the bug for the revision that caused
> the rollback, so it will show correctly. The other revisions will show
> wonkily, and I agree its an issue there.
>
> I assume I've missed a scenario :)
>
> (Dropping to high pending the outcome of this discussion).
>
> ** Changed in: qa-tagger
>   Importance: Critical => High
>
> --
> You received this bug notification because you are a member of Launchpad
> QA, which is subscribed to qa-tagger.
> https://bugs.launchpad.net/bugs/820808
>
> Title:
>  Landings referencing a closed bug are seen as orphaned
>
> Status in QA-tagger tools:
>  Triaged
>
> Bug description:
>  qa-tagger appears to only consider open bugs when looking at landings.
>  Anything without an open bug is seen as orphaned and deployable.
>
>  This is less than ideal when we roll production back after closing
>  bugs, as everything appears to be orphaned and bugs must be reopened
>  before they can be retagged.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qa-tagger/+bug/820808/+subscriptions
>

--
Ursinha (Ursula Junque)
<email address hidden>
<email address hidden>
--
Ubuntu - I am because we are
--
Linux user #289453 - Ubuntu user #31144

[Ursula Junque (ursinha)]

On Thu, Aug 4, 2011 at 5:35 AM, William Grant <email address hidden> wrote:
> Public bug reported:
>
> qa-tagger appears to only consider open bugs when looking at landings.
> Anything without an open bug is seen as orphaned and deployable.
>
> This is less than ideal when we roll production back after closing bugs,
> as everything appears to be orphaned and bugs must be reopened before
> they can be retagged.

I thought that the bug, once closed, shouldn't be reopened in favor of
filing a new one. As a rollback is "safe", it's ok if it finds no
bugs. Then, the commit that would fix the problem would be linked to a
new recently filed bug. Did I miss anything?

>
> ** Affects: qa-tagger
>     Importance: Undecided
>         Status: New
>
> --
> You received this bug notification because you are a member of Launchpad
> QA, which is subscribed to qa-tagger.
> https://bugs.launchpad.net/bugs/820808
>
> Title:
>  Landings referencing a closed bug are seen as orphaned
>
> Status in QA-tagger tools:
>  New
>
> Bug description:
>  qa-tagger appears to only consider open bugs when looking at landings.
>  Anything without an open bug is seen as orphaned and deployable.
>
>  This is less than ideal when we roll production back after closing
>  bugs, as everything appears to be orphaned and bugs must be reopened
>  before they can be retagged.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qa-tagger/+bug/820808/+subscriptions
>

--
Ursinha (Ursula Junque)
<email address hidden>
<email address hidden>
--
Ubuntu - I am because we are
--
Linux user #289453 - Ubuntu user #31144

[Robert Collins (lifeless)]

This is ultimately caused by bug 494807