Add MySQL 8.4 LTS and 9.0 support

Created on 3 July 2024, 6 months ago
Updated 2 September 2024, 4 months ago

Problem/Motivation

MySQL has released a new version of its database. It is version 8.4 and it has been promoted to a LTS version. MySQL has currently 2 LTS versions. The other one is 8.0. That version will be end of life in April 2026. See: https://en.wikipedia.org/wiki/MySQL
Drupal 12 will have to set the minimum required version for MySQL to at least 8.4. We shall need to do so, because Drupal 12 will be released after MySQL 8.0 will go EOL.

Proposed resolution

Add testing for MySQL 8.4 LTS and create the database image.

Remaining tasks

Do it

User interface changes

New database to test with.

API changes

None

Data model changes

None

📌 Task
Status

Fixed

Component

Database Containers

Created by

🇳🇱Netherlands daffie

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @daffie
  • Assigned to andypost
  • 🇫🇷France andypost

    Base image for `mysql-8` also needs update

    mysql                                       8                           736ced9665e8   39 hours ago        583MB
    mysql                                       8.4                         736ced9665e8   39 hours ago        583MB
    mysql                                       8.0                         0b60ddd8609d   39 hours ago        572MB
    
    • andypost committed d30c83df on dev
      Issue #3458690 by daffie, andypost: Add MySQL 8.4 LTS support
      
  • Issue was unassigned.
  • Status changed to Needs review 6 months ago
  • 🇫🇷France andypost

    Pushed dev image

    - added mysql:8.4 image with updated script to use bash while ! echo > /dev/tcp/localhost/3306; do sleep 1; done to wait for port
    - updated mysql:8 image inline with 8.4 - transition from mysql_safe and fix encodings dir

  • 🇫🇷France andypost

    Filed core issue for testing new images and daily run or default 📌 Add core testing with Mysql 8.4 LTS Needs review

  • Assigned to hestenet
  • 🇫🇷France andypost

    Looks everything works without extra packages, so we can simplify in follow-up other db-images (no extra dependencies to install)

    • andypost committed a87ea2fc on production
      Issue #3458690 by daffie, andypost: Add MySQL 8.4 LTS support
      
      
      (cherry...
    • andypost committed b35c3874 on production
      DB: added Mysql 9.0 #3458690
      
      
      (cherry picked from commit...
  • 🇫🇷France andypost

    Got one failure using 9.0 image https://git.drupalcode.org/issue/drupal-3458878/-/jobs/2462104

    WARNING: Event retrieved from the cluster: 0/8 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 6 Insufficient cpu. preemption: 0/8 nodes are available: 2 Preemption is not helpful for scheduling, 6 No preemption victims found for incoming pod..
    WARNING: Event retrieved from the cluster: 0/10 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 2 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 6 Insufficient cpu. preemption: 0/10 nodes are available: 4 Preemption is not helpful for scheduling, 6 No preemption victims found for incoming pod..
    WARNING: Event retrieved from the cluster: 0/10 nodes are available: 1 node(s) had untolerated taint {karpenter.sh/disruption: disrupting}, 2 node(s) didn't match Pod's node affinity/selector, 7 Insufficient cpu. preemption: 0/10 nodes are available: 3 Preemption is not helpful for scheduling, 7 No preemption victims found for incoming pod..
    WARNING: Event retrieved from the cluster: 0/9 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 7 Insufficient cpu. preemption: 0/9 nodes are available: 2 Preemption is not helpful for scheduling, 7 No preemption victims found for incoming pod..
    WARNING: Event retrieved from the cluster: 0/10 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }, 2 node(s) didn't match Pod's node affinity/selector, 7 Insufficient cpu. preemption: 0/10 nodes are available: 3 Preemption is not helpful for scheduling, 7 No preemption victims found for incoming pod..
    WARNING: Event retrieved from the cluster: 0/10 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 8 Insufficient cpu. preemption: 0/10 nodes are available: 2 Preemption is not helpful for scheduling, 8 No preemption victims found for incoming pod..
    Running after_script 00:01
    Running after script...
  • Issue was unassigned.
  • Status changed to Fixed 4 months ago
  • 🇫🇷France andypost

    Images are ready

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024