Launchpad does not show the correct recent commit in a git repository

[Thomas Bechtold]

I created a merge proposal (MP 400965, private project) against a git repo and merged the code (with lpshipit).
The code got merged (I see that at https://git.launchpad.net/~cloudware/cloudware/+git/$REPO-NAME/commit/?h=main and the commit-sha is d88e0624d .
But when I look at https://code.launchpad.net/~cloudware/cloudware/+git/$REPO-NAME/+ref/main , the recent commit there is ecaeda4 .

So Launchpad does not reflect what's really in git!
And because of that, the MP is still in "needs review" instead of "merged" state.

[Thomas Bechtold (toabctl)]

On https://code.launchpad.net/~cloudware/cloudware/+git/$REPO-NAME , I see a "rescan" button. But rescanning failed

[Thomas Bechtold (toabctl)]

Now rescan passed and the recent commits are correct.
I find this still not very user friendly if you can't rely on what LP is showing you. And finding the "rescan" button is not super intuitive. Anyway - feel free to mark the bug as closed.

[Colin Watson (cjwatson)]

It looks like we have a bcache fault in production. I'm converting this into a question, since it's an operational issue more than a software bug (at least at any layer we control directly).