ci: integration-tests fail on Ubuntu 26 because /etc/init.d/mysql is removed

Open Beginner friendly
  • Is something wrong?
#1,114 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Md-Khursheed is already working on this.

Since Nov 5, 2026.

  • #1116 by @Md-Khursheed — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, github-actions, java, mariadb
Domain
ci-cd

Research direction

Read .github/workflows/test.yml and inspect the integration-tests job, especially its MySQL service and Start MYSQL Server step. The issue reports that the step fails because /etc/init.d/mysql is missing, while the service container already serves the tests on port 8888. Remove the redundant step and confirm the integration tests pass using the configured service.

Written by the indexing model from the issue text.

Description

Problem

The integration-tests job in .github/workflows/test.yml fails on every pull request because the Start MYSQL Server step runs sudo /etc/init.d/mysql start, but the Actions runner image has migrated to Ubuntu 26.04, which no longer ships /etc/init.d/mysql.

Job integration-tests on run #1010 (PR #1091):

Start MYSQL Server
0s
1
Run sudo /etc/init.d/mysql start

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

9
Error: Process completed with exit code 1.

Why it's safe to remove

The same workflow already defines a Docker service container (services.mysql) running mariadb:12.3 on port 8888 (lines 104-113). The tests connect to 127.0.0.1:8888, which Docker forwards to that container. The legacy host-level init.d/mysql step is redundant with the service container.

Evidence it's pre-existing, not PR-specific

Every open PR since Oct 31 hits the same failure, including maintainers' own PRs (#1046, #1045).

Fix

Remove lines 121-122 (Start MYSQL Server step) from .github/workflows/test.yml.

Found while waiting for PR #1091 (JDBC driver fix for #1082) to pass CI.

Dominant language
Java
Stars
1.5k
Forks
530
Avg merge
1d 1h
Merged PRs (30d)
61

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OWASP/SecurityShepherd

All issues in OWASP/SecurityShepherd

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.