ActiveRecord::Migration.maintain_test_schema! ignore ssl_mode disabled

[yk-eta]

Steps to reproduce

create a project with mysql connection, run rspec test

Expected behavior

did not raise SSL error

Actual behavior

raised error

Failure/Error: ActiveRecord::Migration.maintain_test_schema!

ActiveRecord::ConnectionNotEstablished:
  TLS/SSL error: SSL is required, but the server does not support it

System configuration

config/database.yml

default: &default
  pool: 5
  adapter: mysql2
  encoding: utf8mb4
  charset: utf8mb4
  collation: utf8mb4_bin
  reconnect: false
  username: xxxx
  password: xxxx
  host: xxxx
  port: xxxx
  database: xxxx
  ssl_mode: disabled

database: 10.4.25-MariaDB libmysql - mysqlnd 8.1.10
ruby: 3.4.3
rails: 7.2.2.1
mysql2: 0.5.6

[pirj]

Does the same occur when you run ‘rails db:migrate’?
My assumption is that this has nothing to do with rspec-rails (which is also a different repository).
In that case, I’m more inclined you should report it to rails.

Anyway, a detailed backtrace is much appreciated.

[yk-eta]

nope, I can run the system by rails server and rails db:migrate but when bundle exec rspec spec then the error occur

[pirj]

Backtrace, please.

[JonRowe]

This is probably an environment issue, what happens if you run RAILS_ENV=test rails db:migrate

[yk-eta]

I upgraded mariadb to 11.7.2 (which support SSL on connection) and it working without issue, I think the issue happen only when database is not support SSL

[yk-eta]

This is probably an environment issue, what happens if you run RAILS_ENV=test rails db:migrate

don think it having issue, as rails db:create and rails db:setup created both standard and test db

[pirj]

Good to know it worked for you.
If you want to pursue pinning down the root cause, please feel free to reopen and post the detailed backtrace of the failure, or a self-contained reproduction example.

[JonRowe]

on think it having issue, as rails db:create and rails db:setup created both standard and test db

Those commands establish connections in development mode first, where as the one I suggested does not, and if it failed to run would highlight an issue with your test config.

Regardless you've solved your issue and RSpec does not handle database connections so closing.