snap /+authorize for brand new snap package name results in OOPS

Bug #1997565 reported by Dimitri John Ledkov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Andrey Fedoseev

Bug Description

I have a brand new snap building in launchpad.
I clicked on Authorize store uploads as I am happy to start publishing said snap in the store.
I click Begin Authorization and I am presented with an OOOPS.

The OOPS is
lp.snappy.interfaces.snapstoreclient.BadRequestPackageUploadResponse: Snap not found for the given snap name '<<<brand new, unregistered, reserved snap name>>>'

something better than an OOPS would be nice here.

Example OOPS is https://oops.canonical.com/?oopsid=OOPS-c9491f2f28872b50f9a0d02018773155

Tags: lp-snappy

Related branches

Guruprasad (lgp171188)
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
tags: added: lp-snappy
Changed in launchpad:
assignee: nobody → Andrey Fedoseev (andrey-fedoseev)
Changed in launchpad:
status: Triaged → In Progress
Colin Watson (cjwatson)
Changed in launchpad:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.