Compatibility with Scylla 5.2

[lattwood]

Issue

This role doesn't work with ScyllaDB 5.2 on Ubuntu 20.04, due to changes in ScyllaDB packages.

Known Issues

• The ScyllaDB 5.2 apt source specifies the required location of the trusted GPG key, where as previous versions didn't.
  • This complicates any potential fix as older versions of the apt source file will likely require the keys to be added to the default apt trusted keychain.
• scylla_bootparam_setup isn't shipped with Scylla 5.2 anymore, but this role still expects to be able to run it.
  • https://github.com/scylladb/scylla-ansible-roles/blob/9653157222dd30c879bb34aabd1011527d2b11d1/ansible-scylla-node/tasks/common.yml#L162-L164

Background

ScyllaDB 5.2 was released May 4th, 2023 and the Ansible roles are still being tested with 5.1 as of July 28th, 2023.

Solution Ideas

Point the molecule tests at ScyllaDB 5.2 and iterate.

Going forward, run integration tests on the "pre-release" version of ScyllaDB in addition to current ones.

[tarzanek]

the boot param is a dup of https://github.com/scylladb/scylla-ansible-roles/issues/256 let's file a PR to fix it

I will try to look at gpg key problem (we should also get molecule auto tests up to 5.1 / 5.2)

[tarzanek]

https://github.com/scylladb/scylla-ansible-roles/pull/276 is field for bootparam

[tarzanek]

ok, I can repro the gpg problem, solution is as per https://github.com/scylladb/scylla-ansible-roles/pull/232#issuecomment-1665211584 but we will need a new PR for that to support 5.2 / 2023

[tarzanek]

wokaround for the nodes with gpg problem:

sudo mkdir -p /etc/apt/keyrings
sudo gpg --homedir /tmp --no-default-keyring --keyring /etc/apt/keyrings/scylladb.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys d0a112e067426ab2

[tarzanek]

also SM 3.1 suffers by above gpg prob

[vladzcloudius]

wokaround for the nodes with gpg problem:

sudo mkdir -p /etc/apt/keyrings
sudo gpg --homedir /tmp --no-default-keyring --keyring /etc/apt/keyrings/scylladb.gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys d0a112e067426ab2

And don't forget to kill the dirmngr the command above is going to spawn and leave behind:

sudo pkill -9 dirmngr

[tarzanek]

see https://github.com/scylladb/scylladb/issues/14965

[tarzanek]

https://github.com/scylladb/scylla-ansible-roles/issues/279 explicitly calls out the gpg problem