Re-releasing to a branch does not update branch expiration time

Bug #1887818 reported by Daniel Manrique
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snap Store Server
Confirmed
Medium
Unassigned

Bug Description

# Current status
ubuntu@snapcraft:~/minisnap$ snapcraft status hello-roadmr-1
Track Arch Channel Version Revision
latest amd64 stable 2019-08-27-01 161
                 candidate 2019-03-05-02 136
                 beta ↑ ↑
                 edge v2020-06-25-02z 169

# Release a revision into a branch
ubuntu@snapcraft:~/minisnap$ snapcraft release hello-roadmr-1 169 stable/branchy1
Track Arch Channel Version Revision Expires at
latest amd64 stable 2019-08-27-01 161
                 candidate 2019-03-05-02 136
                 beta ↑ ↑
                 edge v2020-06-25-02z 169
                 stable/branchy1 v2020-06-25-02z 169 2020-08-15T14:29:00Z
The 'stable/branchy1' channel is now open.

# Re-Release the same revision into a branch

ubuntu@snapcraft:~/minisnap$ snapcraft release hello-roadmr-1 169 stable/branchy1
Track Arch Channel Version Revision Expires at
latest amd64 stable 2019-08-27-01 161
                 candidate 2019-03-05-02 136
                 beta ↑ ↑
                 edge v2020-06-25-02z 169
                 stable/branchy1 v2020-06-25-02z 169 2020-08-15T14:29:00Z

Notice timestamp was not updated - I would have expected it to update the expiry time by at least a couple of seconds (time between commands).

Daniel Manrique (roadmr)
Changed in snapstore-server:
status: New → Confirmed
importance: Undecided → High
Daniel Manrique (roadmr)
Changed in snapstore-server:
importance: High → Critical
Daniel Manrique (roadmr)
Changed in snapstore-server:
importance: Critical → Medium
Revision history for this message
Tong Shinn (tshinn) wrote :

This seems to have been fixed.

The status of "myapp" in staging is a bit messy, but we can see that the expires_at datetime is updated when I re-released it to 1/edge/branch1:

tshinn@ubuntu-vm:~/myapp$ snapcraft status myapp
Track Arch Channel Version Revision Expires at
latest amd64 stable - -
                 candidate - -
                 beta 0.1 1
                 edge 0.1 1
                 edge/branch1 0.1 1 2022-05-04T07:41:03Z
1 amd64 stable - -
                 candidate - -
                 beta - -
                 edge - -
                 edge/branch1 0.1 1 2022-04-17T03:09:38Z
2 amd64 stable - -
                 candidate - -
                 beta - -
                 edge - -
                 beta/branch2 0.1 1 2022-04-17T03:18:24Z
tshinn@ubuntu-vm:~/myapp$ snapcraft release myapp 1 1/edge/branch1
Track Arch Channel Version Revision Expires at
1 amd64 stable - -
                 candidate - -
                 beta - -
                 edge - -
                 edge/branch1 0.1 1 2022-05-04T07:41:20Z
tshinn@ubuntu-vm:~/myapp$ snapcraft status myapp
Track Arch Channel Version Revision Expires at
latest amd64 stable - -
                 candidate - -
                 beta 0.1 1
                 edge 0.1 1
                 edge/branch1 0.1 1 2022-05-04T07:41:03Z
1 amd64 stable - -
                 candidate - -
                 beta - -
                 edge - -
                 edge/branch1 0.1 1 2022-05-04T07:41:20Z
2 amd64 stable - -
                 candidate - -
                 beta - -
                 edge - -
                 beta/branch2 0.1 1 2022-04-17T03:18:24Z
tshinn@ubuntu-vm:~/myapp$

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.