Skip to content

MySQL migrations checks break on ubuntu-26.04 runners #577

Open

Description

@feanil

ubuntu-latest now resolves to ubuntu-26.04 (rolling out since about 2026-11-09). Several repos have a migrations-check workflow that starts the runner's preinstalled MySQL, and on 26.04 that fails before a single migration runs:

sudo: '/etc/init.d/mysql': command not found

edx-submissions (openedx/edx-submissions#394) and edx-enterprise-data (openedx/edx-enterprise-data#730) are fixed and are the pattern to copy: MySQL 8 runs as a service container with openedx-platform's default database name and credentials, and nothing depends on which MySQL the runner image happens to ship (8.0 on 24.04, 8.4 on 26.04).

Repos still on the old job

Repo Workflow Starts MySQL with Runner State on 2026-11-13
credentials .github/workflows/migrations-mysql8-check.yml sudo /etc/init.d/mysql start ubuntu-latest failing since 2026-11-10
license-manager .github/workflows/mysql8-migrations-check.yml sudo /etc/init.d/mysql start ubuntu-latest failing since 2026-11-09
taxonomy-connector .github/workflows/mysql8-migrations.yml sudo /etc/init.d/mysql start ubuntu-latest failing since 2026-11-11
enterprise-catalog .github/workflows/mysql-migrations-check.yml sudo /etc/init.d/mysql start ubuntu-latest failing since 2026-11-09; openedx/enterprise-catalog#1166 pins ubuntu-24.04
course-discovery .github/workflows/migrations-check-mysql8.yml sudo /etc/init.d/mysql start pinned ubuntu-22.04 passing until the pin moves
edx-notes-api .github/workflows/migrations-mysql8-check.yml sudo service mysql start ubuntu-latest passing on 26.04, service falls through to systemd
edx-enterprise .github/workflows/mysql8-migrations.yml sudo systemctl start mysql.service ubuntu-latest workflow is disabled

Fix

Per repo:

  1. Replace the preinstalled-MySQL steps (Initiate services, Reset mysql password, the CREATE DATABASE line) with a mysql:8 service container. The services: block and the health check are in edx-enterprise-data#730.
  2. Point the migration run at the container: DB_HOST=127.0.0.1, the container's database, user and password.

Pinning ubuntu-24.04 keeps the job green for a while, but 24.04 leaves the runner pool eventually and the job still tests against whatever MySQL the image has.

Tasks

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions