[Bug 1922297] Re: 20.10 to 21.04: snap does not upgrade channel

[Brian Murray]

** Description changed:

  [Impact]
  
  Snaps tracking a stable/ubuntu-$version (other than gnome-3-34-1804 and
  gtk-common-themes) are not upgraded during the release upgrade process.
  
  Per LP: #1827951 and LP: #1748581, it would appear that if a snap is
  tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a
  do-release-upgrade the snap channel should update to the new release.
  Testing of a Google cloud image, from 20.10 to 21.04 the google-cloud-
  sdk does not get updated.
  
  # Expected result
  
  After a do-release-upgrade, the snap channel for google-cloud-sdk should
  be updated from "latest/stable/ubuntu-20.10" to
  "latest/stable/ubuntu-21.04".
  
  # Actual result
  
  After install, the snap continues to track "latest/stable/ubuntu-20.10".
  
  [Test Plan]
  GCE image test
- 
- 1. Boot 20.10 GCE image
- 2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10"
- 3. do-release-upgrade -d
+ --------------
+ 1. Boot 20.04 GCE image
+ 2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.04"
+ 3. do-release-upgrade
  4. accept defaults and reboot
  5. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10"
  
  With the version from -proposed the snap will be tracking
- "latest/stable/ubuntu-21.04"
+ "latest/stable/ubuntu-20.10"
  
- Ubuntu Desktop test (regression test)
- 1. Create an Ubuntu 20.10 installation (w/ ubuntu-desktop)
- 2. Run 'do-release-upgrade -d' to upgrade to Hirsute
- 3. Ensure that the gtk-common-themes (and gnome-3-34-1804) snap is now tracking "latest/stable/ubuntu-21.04" via snap-info
+ Ubuntu (18.04, 20.04) Desktop test (regression test)
+ ----------------------------------------------------
+ 1. Create an Ubuntu 20.04 installation (w/ ubuntu-desktop)
+ 2. Run 'do-release-upgrade -p' to upgrade to Groovy
+ 3. Ensure that the gtk-common-themes (and gnome-3-34-1804) snap is now tracking "latest/stable/ubuntu-20.10" via snap-info
  
- With the version from -proposed the snaps will also be upgraded to
- "latest/stable/ubuntu-21.04".
+ With the version from -proposed all installed snaps which track
+ "latest/stable/ubuntu-20.04" will also be upgraded to
+ "latest/stable/ubuntu-20.10".
+ 
+ Ubuntu (16.04) Desktop test plan (new feature)
+ ----------------------------------------------
+ 1. Create an Ubuntu 16.04 installation w/ ubuntu-desktop
+ 2. Run 'do-release-upgrade' to upgrade to Ubuntu 18.04
+ 3. Run snap list and verify that no snaps are installed
+ 
+ With the version of the release upgrader in -proposed you will have a
+ set of snaps installed which are equivalent to the snaps that are
+ preseeded in Ubuntu 18.04. That list of snaps is:
+ 
+ gnome-3-34-1804, gnome-calculator, gnome-characters, gnome-logs, gnome-
+ system-monitor, and gtk-common-themes.
  
  [Where Problems could occur]
  This could regress the upgrading of snaps for Ubuntu desktop images but we've identified that and created a regression test for that scenario.
  
  # Logs
  
  main.log https://paste.ubuntu.com/p/kbSvM5JMzP/
  screenlog.0 https://paste.ubuntu.com/p/h5kvtcX5Z6/
  apt-term.log https://paste.ubuntu.com/p/gNJVzbtT4Z/

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1922297

Title:
  20.10 to 21.04: snap does not upgrade channel

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  In Progress
Status in ubuntu-release-upgrader source package in Focal:
  In Progress
Status in ubuntu-release-upgrader source package in Groovy:
  In Progress
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Snaps tracking a stable/ubuntu-$version (other than gnome-3-34-1804
  and gtk-common-themes) are not upgraded during the release upgrade
  process.

  Per LP: #1827951 and LP: #1748581, it would appear that if a snap is
  tracking a release channel (e.g. latest/stable/ubuntu-20.10), during a
  do-release-upgrade the snap channel should update to the new release.
  Testing of a Google cloud image, from 20.10 to 21.04 the google-cloud-
  sdk does not get updated.

  # Expected result

  After a do-release-upgrade, the snap channel for google-cloud-sdk
  should be updated from "latest/stable/ubuntu-20.10" to
  "latest/stable/ubuntu-21.04".

  # Actual result

  After install, the snap continues to track
  "latest/stable/ubuntu-20.10".

  [Test Plan]
  GCE image test
  --------------
  1. Boot 20.04 GCE image
  2. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.04"
  3. do-release-upgrade
  4. accept defaults and reboot
  5. snap info google-cloud-sdk --> "latest/stable/ubuntu-20.10"

  With the version from -proposed the snap will be tracking
  "latest/stable/ubuntu-20.10"

  Ubuntu (18.04, 20.04) Desktop test (regression test)
  ----------------------------------------------------
  1. Create an Ubuntu 20.04 installation (w/ ubuntu-desktop)
  2. Run 'do-release-upgrade -p' to upgrade to Groovy
  3. Ensure that the gtk-common-themes (and gnome-3-34-1804) snap is now tracking "latest/stable/ubuntu-20.10" via snap-info

  With the version from -proposed all installed snaps which track
  "latest/stable/ubuntu-20.04" will also be upgraded to
  "latest/stable/ubuntu-20.10".

  Ubuntu (16.04) Desktop test plan (new feature)
  ----------------------------------------------
  1. Create an Ubuntu 16.04 installation w/ ubuntu-desktop
  2. Run 'do-release-upgrade' to upgrade to Ubuntu 18.04
  3. Run snap list and verify that no snaps are installed

  With the version of the release upgrader in -proposed you will have a
  set of snaps installed which are equivalent to the snaps that are
  preseeded in Ubuntu 18.04. That list of snaps is:

  gnome-3-34-1804, gnome-calculator, gnome-characters, gnome-logs,
  gnome-system-monitor, and gtk-common-themes.

  [Where Problems could occur]
  This could regress the upgrading of snaps for Ubuntu desktop images but we've identified that and created a regression test for that scenario.

  # Logs

  main.log https://paste.ubuntu.com/p/kbSvM5JMzP/
  screenlog.0 https://paste.ubuntu.com/p/h5kvtcX5Z6/
  apt-term.log https://paste.ubuntu.com/p/gNJVzbtT4Z/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1922297/+subscriptions