Changed ubuntu-keyring paths breaks upgrade to focal.

https://github.com/CanonicalLtd/landscape-client/pull/89

The customer is asking if there's an update?

Customer has asked again for a further update.

Hi , Do you have any updates ?

The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release

Hirsute is EOL since January 2022, closing that task.

All the others were uploaded.

This bug was fixed in the package landscape-client - 19.12-0ubuntu12

---------------
landscape-client (19.12-0ubuntu12) jammy; urgency=medium

  * d/p/lp1903776-release-upgrade.patch (LP: #1903776)
    - Use /etc/apt/trusted.gpg.d for validating upgrade-tool signature.

 -- Simon Poirier <email address hidden> Wed, 09 Mar 2022 11:02:22 -0500

I personally curious about this statement from the bug description given that it is possible with do-release-upgrade to perform upgrades to just about any release you want.

" * There is no way to directly verify this issue on 20.10 Groovy and later
   (without faking a release) due to the lack of upgrade path to a supported
   LTS."

How exactly does landscape-client go about determining if a release upgrade is available?

Hello Simon, or anyone else affected,

Accepted landscape-client into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/landscape-client/19.12-0ubuntu10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Simon, or anyone else affected,

Accepted landscape-client into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/landscape-client/19.12-0ubuntu4.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Simon, or anyone else affected,

Accepted landscape-client into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/landscape-client/18.01-0ubuntu3.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Verified landscape-client 18.01-0ubuntu3.6 on bionic by updating to the bionic-proposed package.

I registered a new LXD container client on a SaaS account, triggered a release upgrade. The upgrade tool downloaded, validated, launched and the landscape activity completed successfully.

I verified landscape-client 19.12-0ubuntu4.3 from focal-proposed.
I used landscape-server-quickstart from ppa:landscape/19.10 and registered the proposed client against it.
Then I had to enable the upcoming upgrade tool to the server:

# sudo -u landscape psql landscape-standalone-main -c "insert into meta_release (code_name, name, version, date, supported, upgrade_tool_tarball_url, upgrade_tool_signature_url, lts) VALUES ('jammy', 'Jammy Jellyfish', '22.04 LTS', now(), 't', 'http://archive.ubuntu.com/ubuntu/dists/jammy/main/dist-upgrader-all/current/jammy.tar.gz', 'http://archive.ubuntu.com/ubuntu/dists/jammy/main/dist-upgrader-all/current/jammy.tar.gz.gpg', 't')"
# sudo -u landscape psql landscape-standalone-main -c "update meta_release set upgrade_id=(select id from meta_release where code_name='jammy') where code_name in ('focal', 'impish')"

Launching the release upgrade activity from the web UI, the client machine was able to download and validate the upgrade tool and upgraded to jammy succesfully.

I also verified landscape-client 19.12-0ubuntu10.1 from impish-proposed.
I used the same landscape-server-quickstart from ppa:landscape/19.10 as previously, with the same database query to enable upgrading.

Again, upgrade tool downloaded and validated successfully on the proposed version, with the upgrade successful and the
logs confirming the success:

# tail -f /var/log/landscape/release-upgrader.log
2022-03-29 19:58:48,927 DEBUG [MainThread] Started firing run.
2022-03-29 19:58:48,927 DEBUG [MainThread] Finished firing run.
2022-03-29 19:58:49,793 INFO [MainThread] Successfully fetched upgrade-tool files
2022-03-29 19:58:49,817 INFO [MainThread] Successfully verified upgrade-tool tarball
2022-03-29 20:09:34,616 INFO [MainThread] Queuing message with release upgrade results to exchange urgently.
2022-03-29 20:09:35,028 DEBUG [MainThread] Started firing stop.
2022-03-29 20:09:35,028 DEBUG [MainThread] Finished firing stop.

This bug was fixed in the package landscape-client - 19.12-0ubuntu10.1

---------------
landscape-client (19.12-0ubuntu10.1) impish; urgency=medium

  * d/p/0006-lp1903776-release-upgrade.patch (LP: #1903776)
    - Use /etc/apt/trusted.gpg.d for validating upgrade-tool signature.

 -- Simon Poirier <email address hidden> Thu, 10 Feb 2022 18:46:26 -0500

The verification of the Stable Release Update for landscape-client has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package landscape-client - 19.12-0ubuntu4.3

---------------
landscape-client (19.12-0ubuntu4.3) focal; urgency=medium

  * d/p/0004-lp1903776-release-upgrade.patch (LP: #1903776)
    - Use /etc/apt/trusted.gpg.d for validating upgrade-tool signature.

 -- Simon Poirier <email address hidden> Mon, 14 Feb 2022 18:56:31 -0500

This bug was fixed in the package landscape-client - 18.01-0ubuntu3.6

---------------
landscape-client (18.01-0ubuntu3.6) bionic; urgency=medium

  * d/p/1903776-release-upgrade.patch (LP: #1903776)
    - Use /etc/apt/trusted.gpg.d for validating upgrade-tool signature.

 -- Simon Poirier <email address hidden> Tue, 17 Nov 2020 19:06:42 -0500