Fundraising/techops/procedures/services-trino upgrade

Like other packages, we use build_package and risky_package_updater to upgrade trino to a new version. Note that new trino versions may also require updating the JDK version.

Prep

• Check available trino version on the frpm host: check_reprepro_packages
• Especially in vb, make sure you have enough disk space!
• If running on windows/ WSL, make sure kleopatra is running so you can input the gpg key phrase

Upgrade

Dev/ VB

Of course, test in vb first!

We need to upgrade both trino-cli and trino-server

1. On the frpm host: build_package trino-cli and build_package trino-server
   1. Would you like to push the package to the repo using reprepro? (y/[n]) : y
2. If needed, upgrade the temurin JDK version by pinning the new version at the top of /etc/puppet/modules/base/manifests/package/temurin_jdk.pp after $release
   1. no need to run puppet-merge
3. on the relevant frans* hosts, run sudo risky_package_updater -ap to automatically upgrade trino and temurin. you may need to run it twice for temurin to upgrade to the new pinned version
   1. use dpkg -l to check the versions. if the versions don’t look right, try running apt-get update and then apt-get dist-upgrade manually on the host
4. Once the versions look right, restart trino on each frans* host
5. finally, test trino by using trino-cli and try to run some queries or kick off a dbt job
   1. you can also check the version of each node in the workers page of the trino ui

Prod

After testing in vb, let's upgrade in prod! The steps are largely the same except we arent live hacking in prod, so we actually need to commit and merge the change to temurin_jdk.pp

Troubleshooting

(vb)astein@frpm1002:~$ build_package trino-server
Didn't find /home/astein/packages/trino-server/debian-1!

You probably accidentally deleted important metadata files in ~/packages/. From that dir, run git reset --hard