| 2022-07-12 20:01:38 |
Brian Murray |
bug |
|
|
added bug |
| 2022-07-12 20:02:10 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu): milestone |
|
ubuntu-22.04.1 |
|
| 2022-07-12 20:06:17 |
Brian Murray |
tags |
|
rls-jj-incoming |
|
| 2022-07-12 20:12:45 |
Jeremy Bícha |
bug |
|
|
added subscriber Jeremy Bicha |
| 2022-07-12 20:26:58 |
Brian Murray |
bug |
|
|
added subscriber Canonical's Ubuntu QA |
| 2022-07-14 15:29:39 |
Lukas Märdian |
tags |
rls-jj-incoming |
fr-2551 rls-jj-incoming |
|
| 2022-07-14 15:31:06 |
Lukas Märdian |
nominated for series |
|
Ubuntu Kinetic |
|
| 2022-07-14 15:31:06 |
Lukas Märdian |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Kinetic) |
|
| 2022-07-14 15:31:06 |
Lukas Märdian |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-07-14 15:31:06 |
Lukas Märdian |
bug task added |
|
ubuntu-release-upgrader (Ubuntu Jammy) |
|
| 2022-07-14 15:31:12 |
Lukas Märdian |
tags |
fr-2551 rls-jj-incoming |
fr-2551 |
|
| 2022-07-15 19:27:14 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Jammy): milestone |
|
ubuntu-22.04.1 |
|
| 2022-07-15 19:27:18 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Kinetic): milestone |
ubuntu-22.04.1 |
|
|
| 2022-07-15 19:27:24 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Kinetic): assignee |
|
Brian Murray (brian-murray) |
|
| 2022-07-15 19:27:26 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Jammy): assignee |
|
Brian Murray (brian-murray) |
|
| 2022-07-15 21:52:59 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Jammy): status |
New |
In Progress |
|
| 2022-07-15 21:53:01 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Kinetic): status |
New |
In Progress |
|
| 2022-07-15 21:53:05 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Kinetic): importance |
Undecided |
High |
|
| 2022-07-15 21:53:07 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-07-19 15:17:52 |
Łukasz Zemczak |
ubuntu-release-upgrader (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-07-19 15:17:53 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-07-19 15:17:55 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2022-07-19 15:18:01 |
Łukasz Zemczak |
tags |
fr-2551 |
fr-2551 verification-needed verification-needed-jammy |
|
| 2022-07-19 16:55:49 |
Brian Murray |
description |
During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log:
2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded
2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed
2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded
The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. |
[Description]
The snap gnome-3-34-1804 is not longer seeded in Ubuntu 22.04 but the distribution upgrade process is not aware of this and will leave the snap installed after the upgrade.
[Test Plan]
Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed.
After the upgrade completes the snap gnome-3-34-1804 should no long be installed. (Check out output of snap list and also check /var/log/dist-upgrade/main.log for the message "removing snap gnome-3-34-1804".)
[Regression Potential]
During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log:
2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded
2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed
2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded
The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. |
|
| 2022-07-19 17:20:02 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Jammy): milestone |
ubuntu-22.04.1 |
ubuntu-22.04.2 |
|
| 2022-07-19 17:20:07 |
Brian Murray |
ubuntu-release-upgrader (Ubuntu Jammy): status |
Fix Committed |
Triaged |
|
| 2022-07-19 18:15:32 |
Brian Murray |
description |
[Description]
The snap gnome-3-34-1804 is not longer seeded in Ubuntu 22.04 but the distribution upgrade process is not aware of this and will leave the snap installed after the upgrade.
[Test Plan]
Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed.
After the upgrade completes the snap gnome-3-34-1804 should no long be installed. (Check out output of snap list and also check /var/log/dist-upgrade/main.log for the message "removing snap gnome-3-34-1804".)
[Regression Potential]
During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log:
2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded
2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed
2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded
The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. |
[Description]
The snap gnome-3-34-1804 is no longer seeded in Ubuntu 22.04 but the distribution upgrade process is not aware of this and will leave the snap installed after the upgrade.
[Test Plan]
Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed.
After the upgrade completes the snap gnome-3-34-1804 should no long be installed. (Check out output of snap list and also check /var/log/dist-upgrade/main.log for the message "removing snap gnome-3-34-1804".)
[Regression Potential]
Other snaps may depend on the gnome-3-34-1804 snap (slack for instance) and removing gnome-3-34-1804 would then make those snaps unusable. Subsequently, the test plan involves installing the slack snap and then upgrading and ensuring it still launches.
Original Description
--------------------
During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log:
2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded
2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed
2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded
The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. |
|
| 2022-07-19 18:17:15 |
Brian Murray |
description |
[Description]
The snap gnome-3-34-1804 is no longer seeded in Ubuntu 22.04 but the distribution upgrade process is not aware of this and will leave the snap installed after the upgrade.
[Test Plan]
Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed.
After the upgrade completes the snap gnome-3-34-1804 should no long be installed. (Check out output of snap list and also check /var/log/dist-upgrade/main.log for the message "removing snap gnome-3-34-1804".)
[Regression Potential]
Other snaps may depend on the gnome-3-34-1804 snap (slack for instance) and removing gnome-3-34-1804 would then make those snaps unusable. Subsequently, the test plan involves installing the slack snap and then upgrading and ensuring it still launches.
Original Description
--------------------
During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log:
2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded
2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed
2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded
The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. |
[Description]
The snap gnome-3-34-1804 is no longer seeded in Ubuntu 22.04 but the distribution upgrade process is not aware of this and will leave the snap installed after the upgrade.
[Test Plan]
Test 1
------
Using the dist-upgrader tarball from http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/dist-upgrader-all/current/ on an Ubuntu 20.04 LTS system upgrade to Ubuntu 22.04 LTS. (Using the tarball is necessary because one cannot use 'do-release-upgrade -d and -p' simultaneously.) The tarball should be manually extracted into /tmp/ and the file (or symlink) named 'jammy' should be executed.
After the upgrade completes the snap gnome-3-34-1804 should no long be installed. (Check out output of snap list and also check /var/log/dist-upgrade/main.log for the message "removing snap gnome-3-34-1804".)
Test 2
------
Complete the same test as above but before upgrading install the slack snap. After the upgrade completes gnome-3-34-1804 should still be installed and the slack snap should still launch.
[Regression Potential]
Other snaps may depend on the gnome-3-34-1804 snap (slack for instance) and removing gnome-3-34-1804 would then make those snaps unusable. Subsequently, the test plan involves installing the slack snap and then upgrading and ensuring it still launches.
Original Description
--------------------
During an upgrade from Ubuntu 20.04 to Ubuntu 22.04 I noticed the following in the log:
2022-07-12 12:11:02,144 DEBUG install of snap firefox succeeded
2022-07-12 12:11:02,735 DEBUG refresh of snap gnome-3-34-1804 failed
2022-07-12 12:11:03,372 DEBUG refresh of snap gtk-common-themes succeeded
The refresh of the snap gnome-3-34-1804 failed because there is no ubuntu-22.04 channel for it. I don't think the snap is needed any longer and it should switch from the "seeded" section to the "unseeded" section in deb2snap.json. |
|
| 2022-07-20 18:26:48 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Kinetic): status |
In Progress |
Fix Released |
|
| 2022-07-22 23:13:03 |
Brian Murray |
tags |
fr-2551 verification-needed verification-needed-jammy |
fr-2551 verification-done verification-done-jammy |
|
| 2022-07-26 11:32:28 |
Launchpad Janitor |
ubuntu-release-upgrader (Ubuntu Jammy): status |
Triaged |
Fix Released |
|
| 2022-07-26 11:32:35 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-08-02 18:41:36 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/427735 |
|
