Launchpad itself

launchpad code rescans failing

Bug #634451 reported by dobey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Tim Penhey
Launchpad itself 10.10

Bug Description

At some point today, it appears the launchpad code scanning has stopped being reliable. The following branches are having issues with rescans:

https://code.edge.launchpad.net/~verterok/ubuntuone-client/fix-598189
https://code.edge.launchpad.net/~rodrigo-moya/ubuntuone-client/fix-613219
https://code.edge.launchpad.net/~nataliabidart/ubuntuone-client/fix-u1sync

There are more, but I presume they all have similar issues.

Related branches

lp://staging/~thumper/launchpad/scanner-permissions
Michael Hudson-Doyle: Approve
Diff: 61 lines (+13/-0)
3 files modified
database/schema/security.cfg (+1/-0)
lib/lp/codehosting/scanner/tests/test_buglinks.py (+9/-0)
lib/lp/codehosting/scanner/tests/test_bzrsync.py (+3/-0)
Tim Penhey (thumper)
Changed in launchpad:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Tim Penhey (thumper)
affects: launchpad → launchpad-code
Changed in launchpad-code:
assignee: Tim Penhey (thumper) → nobody
Tim Penhey (thumper)
tags: added: branch-scanner oops
Revision history for this message
Tim Penhey (thumper) wrote :

Permission fix applied to production already. Branch has been landed that ensures the fix sticks.

Changed in launchpad-code:
assignee: nobody → Tim Penhey (thumper)
milestone: none → 10.10
status: In Progress → Fix Released
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit

Fixed in stable r11525 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11525>.

Ursula Junque (ursinha)
tags: added: qa-needstesting
Robert Collins (lifeless)
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Aaron Bentley (abentley) wrote :

This appears to have broken in production, but I gotten Stefan to manually re-apply the change to production and triggered scans of the affected branches.

Revision history for this message
Tim Penhey (thumper) wrote :

I bet this happened during the postgresql 8.4 upgrade :-(

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

Yes. The PG 8.4 upgrades where done before the rollout, and would have been using the the previous cycles security.cfg file. The manually applied changes should have been reapplied as part of the upgrade but where not.

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 634451] Re: launchpad code rescans failing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/14/2010 02:05 AM, Stuart Bishop wrote:
> Yes. The PG 8.4 upgrades where done before the rollout, and would have
> been using the the previous cycles security.cfg file. The manually
> applied changes should have been reapplied as part of the upgrade but
> where not.

Even using the current production-stable's security.cfg file would have
avoided this issue.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAky3B5oACgkQ0F+nu1YWqI2PGwCgiLAW3dvi3R42uq0+5HbijI+n
zpQAn0ZEEGRSS+ezOLzdKsC8bW7O2J98
=qtO+
-----END PGP SIGNATURE-----

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.