All of Wikimedia production is already on that – T356960: Upgrade hosts to MariaDB 10.6. Being still on 10.3, which is old and EOL, risks us missing bugs.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T366644 Raise MediaWiki's MariaDB requirement to 10.6 | |||
| Open | None | T366646 Raise Quibble jobs' tested version of MariaDB to 10.6 | |||
| Open | None | T362705 Migrate Quibble images from bullseye to bookworm | |||
| Open | Jdforrester-WMF | T335766 Migrate Quibble images from buster to bullseye | |||
| Resolved | hashar | T366799 Quibble jobs fail on bullseye images in QUnit job: "Multiple targets are not supported" | |||
| Resolved | hashar | T369146 Quibble CI images based on Buster fail to build due to sury.org dropping support |
Event Timeline
Comment Actions
We'll get this for "free" when we complete T335766: Migrate Quibble images from buster to bullseye and then T362705: Migrate Quibble images from bullseye to bookworm – buster comes with 10.3, bullseye comes with 10.5, and it's not until bookworm that we get to or over 10.6 (specifically, to 10.11). Meh.
Comment Actions
In all those years, I don't think I have cared much about MariaDB in the CI image beside:
- setting sql_mode = 'TRADITIONAL' T119371
- Using binary character set and collation to match production T193222
If production went to 10.6 and Debian does not provide it, I imagine SRE went to build 1.6 version for Bullseye or Bookworm. If our CI images are based on the same Debian system, we can install that MariaDB instead of the stock Debian version, else I guess we can ignore?
Comment Actions
In production we run 10.6. We have packages for Bullseye, but we encourage to go to Bookworm directly if possible.