Puzzling error when snap projects are disputed

Bug #1670368 reported by Didier Roche-Tolomelli
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server

Bug Description

<context: I though I had registered chuck-norris-webserver snap name a long time ago>

1. create a snap from branch on launchpad, check uploads on build to chuck-norris-webserver
-> SSO auth, telling the access is granting:
/!\ I didn't know at the time, but I didn't register that project, however, it seems the check is only to ensure the snap name is registered, not if you have access to it.
2. build on launchpad -> upload fail on permission error
3. filed a dispute and get it acked
4. build on launchpad -> upload still fails on 403 (I guess targetting the snap ID instead of name, so the renamed snap)
5. edit -> don't upload to store, save. Edit -> upload to store, SSO ack, save.
Further uploads are ok.

I guess the error message should be clearer on why a 403 is received, with possible advice on what to do to fix it.

Changed in snapstore:
status: New → In Progress
assignee: nobody → Facundo Batista (facundo)
Changed in snapstore:
assignee: Facundo Batista (facundo) → nobody
status: In Progress → New
William Grant (wgrant)
tags: added: snap-registration
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.