I'm preparing to upgrade nodes from 3.11.17 to 4.1.7. I've done the upgrade successfully by hand with some dev nodes, but I am wanting to make this more repeatable with Ansible. I am running on Ubuntu servers, so I have to fight with apt auto starting the service. Wondering what would be the most kosher process of doing these upgrades without apt tossing default files at me and possibly messing stuff up. My thoughts are: 1. drain and stop one node 2. Template in my necessary cassandra.yaml and rack properties files 3. Do the install of cassandra 4.1.7 4. Cope with apt auto starting cassandra Does this spell disaster? My data isn't in the default path of the config that comes from the package maintainer (/var/lib/cassandra), and some of my config variables are no longer present in 4.1 so I would expect cassandra to crash on startup, seeing the unrecognized variables (which I came across with my dev tests). What I would REALLY like is to install cassandra and give it a good look over before starting, but I am not afforded that luxury. In numerous tests, stopping cassandra immediately after a successful install did not work, cassandra would persist.

I was trying to install PostgreSQL 14 database in Ubuntu 22.04 version as per the steps provided in the official Postgres site. But while updating the package list, I'm getting an error message. Could someone please help me to resolve this issue? All the steps that I executed are given below: root@abc02:~# sudo sh -c 'echo "deb [signed-by=/usr/share/postgresql-common/pgdg/apt.postgresql.org.asc] https://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list' root@abc02:~# sudo apt install curl ca-certificates Reading package lists... Done Building dependency tree... Done Reading state information... Done ca-certificates is already the newest version (20230311ubuntu0.22.04.1). curl is already the newest version (7.81.0-1ubuntu1.16). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@abc02:~# sudo install -d /usr/share/postgresql-common/pgdg root@abc02:~# sudo curl -o /usr/share/postgresql-common/pgdg/apt.postgresql.org.asc --fail https://www.postgresql.org/media/keys/ACCC4CF8.asc % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4812 100 4812 0 0 4221 0 0:00:01 0:00:01 --:--:-- 4224 root@abc02:~# sudo apt update Get:1 https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease [129 kB] Err:1 https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease Unknown error executing apt-key Reading package lists... Done W: GPG error: https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease: Unknown error executing apt-key E: The repository 'https://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Additional details- I can see contents in /usr/share/postgresql-common/pgdg/apt.postgresql.org.asc root@abc02:/usr/share/postgresql-common/pgdg# cat apt.postgresql.org.asc -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBE6XR8IBEACVdDKT2HEH1IyHzXkb4nIWAY7echjRxo7MTcj4vbXAyBKOfjja UrBEJWHN6fjKJXOYWXHLIYg0hOGeW9qcSiaa1/rYIbOzjfGfhE4x0Y+NJHS1db0V