403 from SSO/api/v2/tokens/refresh results in OOPS rather than helpful email

[Nicholas Skaggs]

See https://code.launchpad.net/~juju-qa-bot/+snap/juju-candidate/+build/24410 for example. Note, uploads to the edge channel for same store package is successful.

Adding notes from Colin:

the 403 is from /api/v2/tokens/refresh, which is a bit mysterious
please quote OOPS-83ee077e2b4401cf4d156e4ce3823bc5
(though the statement log in that OOPS is junk, for reasons; but it at least includes a traceback)

[Nicholas Skaggs (nskaggs)]

I'll note that this appears to affect only candidate channel. All others upload properly.

[Nicholas Skaggs (nskaggs)]

This is happening regularly now:

See as an example.

https://code.launchpad.net/~juju-qa-bot/+snap/juju-edge/+build/26566

[Colin Watson (cjwatson)]

As far as I can tell, this is happening because the account that was used to authorise uploads of this snap to the store was ~jujuisquality-deactivatedaccount, which is (as the name suggests) a deactivated Launchpad account, which prevents refreshing time-limited credentials issued for it. To fix this, it will be necessary to reauthorise uploads of that snap using a different account. You can do so using (for example) the following URL, though it may also be necessary to arrange that the account that you do this with has permission to upload the snap in question to the store:

  https://code.launchpad.net/~juju-qa-bot/+snap/juju-edge/+authorize

I think the only Launchpad bug here is that the error is not clearer; we should respond to this not with an OOPS but with an email indicating that you need to reauthorise uploads.

[Launchpad QA Bot (lpqabot)]

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