Comment 4 for bug 1904212

Hi,

We also got the same error back from the store when publishing a snap, not revision 1 but 25 in this case. It's a Brand Store. Here is our output from CI:

$ snapcraft upload .dist/*.snap --release edge
Preparing to upload 'osp-test-pc_20.4.26_amd64.snap'.
After uploading, the resulting snap revision will be released to 'edge' when it passes the Snap Store review.
Install the review-tools from the Snap Store for enhanced checks before uploading this snap.
Pushing 'osp-test-pc_20.4.26_amd64.snap' [===============================] 100%
Ready to release!
Revision 25 of 'osp-test-pc' created.
Processing...|
Sorry, an error occurred in Snapcraft:
No revision information for 25
Traceback (most recent call last):
  File "/snap/snapcraft/current/bin/snapcraft", line 33, in <module>
    sys.exit(load_entry_point('snapcraft==4.3', 'console_scripts', 'snapcraft')())
  File "/snap/snapcraft/current/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/snap/snapcraft/current/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/snap/snapcraft/current/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/snap/snapcraft/current/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/snap/snapcraft/current/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/snap/snapcraft/current/lib/python3.6/site-packages/snapcraft/cli/store.py", line 198, in upload
    snap_revision
  File "/snap/snapcraft/current/lib/python3.6/site-packages/snapcraft/storeapi/v2/channel_map.py", line 317, in get_revision
    raise ValueError(f"No revision information for {revision_number!r}")
ValueError: No revision information for 25
You can find the traceback in file '/tmp/tmpsq5sctfq/trace.txt'.

A working job, which include other sundry set-up, took 33 seconds, whereas this job took 52. Perhaps there is something timing out on the store side ?

When we checked, the revision had been published.

A subsequent push creating a new revision was also fine.

Cheers,
Just