Instance Ubuntu 22.04 GPG error trusted.gpg keyring

Hi,
Newly deployed UBUNTU 20.04 from Morpheus templates give issue of warning of GPG signature.
We were ignoring this for quite a while but now due to automation we are facing this tickets of customer for resolving this issue. It seems to me small issue that is why i didn’t raise the ticket instead came here for solution.

root@tryme02:~# apt update
Ign:1 https://mymorpheus.io/apt morpheus InRelease
Hit:2 https://mymorpheus.io/apt morpheus Release
Get:3 https://mymorpheus.io/apt morpheus Release.gpg [473 B]
Ign:3 https://mymorpheus.io/apt morpheus Release.gpg
Hit:4 Index of /ubuntu jammy InRelease
Hit:5 Index of /ubuntu jammy-updates InRelease
Hit:6 Index of /ubuntu jammy-backports InRelease
Hit:7 Index of /ubuntu jammy-security InRelease
Fetched 473 B in 1s (429 B/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
170 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
W: https://mymorpheus.io/apt/dists/morpheus/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: https://mymorpheus.io/apt morpheus Release: The following signatures were invalid: EXPKEYSIG 239FF1B456AB73A6 Morpheus Data LLC Releases releases@morpheusdata.com

Please provide both fix.

  1. Permanent fix from the instance itself.
  2. fix after deployment manually with commands.

This is fixed in newer versions of Morpheus. To push the fix to individual servers, you should update the Morpheus Agent on impacted systems.

1 Like

Can i know exactly which version of morpheus it is fixed in ?
As i am using V. 6.0.6

Thank you for quickest response :slight_smile:

According to the release notes for your current branch, it looks like GPG keys were updated in 6.0.8:

https://docs.morpheusdata.com/en/6.0.8/release_notes/current.html

In looking at our dev ticket system, I can also see a related fix/update for GPG keys was also included in the 6.0.9 release so I would suggest upgrading to that, if not the latest and greatest for that branch (6.0.11 currently). These fixes were also included in the 6.2.4 and 6.3.1 releases as well, in case you are looking at upgrading to a more recent branch release in the future.

Hope that helps!

2 Likes