Upgrade the lodgeit mariadb to 10.11

I have tested this upgrade on a held node going straight from 10.4 to
10.11 in one go. The resulting logs can be found in this paste [0].

The resulting backups of system tables are small enough that it seems
reasonable to keep those enabled (though they can be disabled). Also, we
can either land this change and let docker-compose do the upgrade for
us, or we can put the host in the emergency file, do the upgrade by
hand, then merge this change to reflect the new state of the world.
One advantage to doing this by hand is that we can manually run a db
backup with the service turned off to avoid any lost data between the
time the upgrade occurs and the time of our last backup should anything
go wrong.

In either case we should probably double check that db backups look good
in borg before proceeding. Comments on approach are very much welcome.

[0] https://paste.opendev.org/show/bWhZZH97IMLv44eeiWlB/

Change-Id: I1bfcaeb9b90838a80d002732215f45a14a158fed
This commit is contained in:
Clark Boylan 2024-02-19 09:01:10 -08:00
parent 5b8dd8b96c
commit 7526de2410

View File

@ -2,7 +2,7 @@ version: '2'
services: services:
mariadb: mariadb:
image: docker.io/library/mariadb:10.4 image: docker.io/library/mariadb:10.11
network_mode: host network_mode: host
restart: always restart: always
environment: environment:
@ -10,6 +10,7 @@ services:
MYSQL_DATABASE: "{{ lodgeit_db_dbname }}" MYSQL_DATABASE: "{{ lodgeit_db_dbname }}"
MYSQL_USER: "{{ lodgeit_db_username }}" MYSQL_USER: "{{ lodgeit_db_username }}"
MYSQL_PASSWORD: "{{ lodgeit_db_password }}" MYSQL_PASSWORD: "{{ lodgeit_db_password }}"
MARIADB_AUTO_UPGRADE: 1
command: [ command: [
'--wait_timeout=28800', '--wait_timeout=28800',
] ]