| 2023-08-15 07:36:48 |
Simon Fels |
description |
We have a snap named "anbox-cloud-tests" on the snap store which has a set of versioned tracks (1.9 - 1.21) and nothing in the latest/{stable,candidate,beta,edge} channels. Latest is also set as the default track.
We now download a snap from a channel (rev 592 from 1.17/edge in this case) and install it together with its assertion:
$ snap download --revision=592 anbox-cloud-tests
$ snap ack anbox-cloud-tests_592.assert
$ snap install anbox-cloud-tests_592.snap
anbox-cloud-tests 1.17.1-alpha.9+gitd9a1e82 from Canonical✓ installed
As a next step we run a manual refresh (but can also be an automatic refresh, does not matter):
$ snap refresh anbox-cloud-tests
anbox-cloud-tests 1.14.1-fix1 from Canonical✓ refreshed
Channel for anbox-cloud-tests is closed; temporarily forwarding to stable
The snap is now incorrectly refreshed to the 1.14/stable track (see `snap info anbox-cloud-tests`) and snapd also fails to indicate what channel it has the snap refreshed to.
I have not expected the refresh to be successful as I installed the snap without an associated channel. A `snap refresh anbox-cloud` should have failed as no channel is associated and should have required a --channel argument to succeed. The info message from refresh also is confused about what it is actually doing.
I am not sure if this is expected behavior, a bug or both. |
We have a snap named "anbox-cloud-tests" on the snap store which has a set of versioned tracks (1.9 - 1.21) and nothing in the latest/{stable,candidate,beta,edge} channels. Latest is also set as the default track.
We now download a snap from a channel (rev 592 from 1.17/edge in this case) and install it together with its assertion:
$ snap download --revision=592 anbox-cloud-tests
$ snap ack anbox-cloud-tests_592.assert
$ snap install anbox-cloud-tests_592.snap
anbox-cloud-tests 1.17.1-alpha.9+gitd9a1e82 from Canonical✓ installed
$ snap list
Name Version Rev Tracking Publisher Notes
anbox-cloud-tests 1.17.1-alpha.9+gitd9a1e82 592 - canonical✓ -
As a next step we run a manual refresh (but can also be an automatic refresh, does not matter):
$ snap refresh anbox-cloud-tests
anbox-cloud-tests 1.14.1-fix1 from Canonical✓ refreshed
Channel for anbox-cloud-tests is closed; temporarily forwarding to stable
The snap is now incorrectly refreshed to the 1.14/stable track (see `snap info anbox-cloud-tests`) and snapd also fails to indicate what channel it has the snap refreshed to. Looking at the list of installed snaps there is still no tracking channel:
$ snap list
Name Version Rev Tracking Publisher Notes
anbox-cloud-tests 1.14.1-fix1 338 - canonical✓ -
I have not expected the refresh to be successful as I installed the snap without an associated channel. A `snap refresh anbox-cloud` should have failed as no channel is associated and should have required a --channel argument to succeed. The info message from refresh also is confused about what it is actually doing.
I am not sure if this is expected behavior, a bug or both. |
|
