weird cohort behaviour (time lag?)

Bug #1846135 reported by John Lenton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
Fix Released
Critical
William Grant

Bug Description

$ COH=$( snap create-cohort kubectl | jmes 'cohorts.kubectl."cohort-key"' )
$ snap install kubectl --classic --channel=1.16 --cohort=$COH
error: snap "kubectl" is not available on 1.16/stable but is available to install on the following
       tracks:

       latest/stable snap install --stable kubectl
       1.15/stable snap install --channel=1.15 kubectl
       1.14/stable snap install --channel=1.14 kubectl
       1.13/stable snap install --channel=1.13 kubectl
       1.12/stable snap install --channel=1.12 kubectl
       1.11/stable snap install --channel=1.11 kubectl
       1.10/stable snap install --channel=1.10 kubectl
       1.9/stable snap install --channel=1.9 kubectl
       1.8/stable snap install --channel=1.8 kubectl
       1.7/stable snap install --channel=1.7 kubectl
       1.6/stable snap install --channel=1.6 kubectl
       1.5/stable snap install --channel=1.5 kubectl

       Please be mindful that different tracks may include different features. Get more information
       with 'snap info kubectl'.

... wait a few minutes ...

$ snap install kubectl --classic --channel=1.16 --cohort=$COH
kubectl (1.16/stable) 1.16.0 from Canonical✓ installed

Revision history for this message
William Grant (wgrant) wrote :

It seems to actually be intermittent, not specifically lagged.

Internal logs from an erroneously failed request: https://pastebin.canonical.com/p/4zCnR2T4KD/

Changed in snapstore:
assignee: nobody → William Grant (wgrant)
importance: Undecided → Critical
status: New → Triaged
tags: added: snapdevicegw
tags: added: snap-releases
William Grant (wgrant)
Changed in snapstore:
status: Triaged → In Progress
William Grant (wgrant)
Changed in snapstore:
status: In Progress → Fix Committed
William Grant (wgrant)
Changed in snapstore:
status: Fix Committed → 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.