OOPS on MP pages when Turnip is not fully available

[Alexandre Gomes]

When accessing https://code.launchpad.net/~ack/maas/+git/maas/+merge/397784 and https://code.launchpad.net/~ack/maas/+git/maas/+merge/398126 I get OOPSes.

The most recent OOPS-ids are:
OOPS-4585acd8c565e9d771b16f424adb08a8
OOPS-042d3538df640493fe89b3ba0b573477

[Thiago F. Pappacena (pappacena)]

The page is OOPSing when Launchpad tries to get git log from Turnip, which returns a 500 error.

The information that comes from Turnip to fill MP page is not totally necessary. The user should be able to see the MP page, even if some information from Turnip is not immediately available.

[Thiago F. Pappacena (pappacena)]

I have changed the bug's title to describe a bit better the problem and give a hint of what we are willing to achieve here.

[Thiago F. Pappacena (pappacena)]

About the problem on Turnip side, it seems that the repository is in some sort of corrupt state, raising this error when doing store.get_log (on repo.wak(start) call, to be more precise):

KeyError: 'object not found - no match for id (2c8c1224b9e4f4ac311fce39dcdcabcea790c1a4)'

2c8c1224b9e4f4ac311fce39dcdcabcea790c1a4 is the commit ID accepted by one of the above MPs. I've tried to clone the repository locally, and couldn't find such commit ID (although the cloned repository seems to be working just fine).

[Colin Watson (cjwatson)]

Perhaps the commit ID in question was just rebased out of existence, force-pushed, and then eventually disappeared entirely from the repository by way of a repack? Something like that seems at least possible.