Fix TLS verify error when gh-ost discovers the replication master by petervandoros · Pull Request #1487 · github/gh-ost

added 6 commits

January 2, 2025 13:04
…Name property

Ensure the ServerName TLS property matches the new connection
instance key hostname to avoid TLS verify errors like the following:

2025-01-02 02:07:26 FATAL tls: failed to verify certificate: x509: certificate is valid for [old host], not [new host]

This is only one part of the fix for this issue. The second part,
registering TLS Config with the mysql driver, will come in
subsequent commits.
… driver

This allows us to register TLS configuration is the various places
where connection configs are created and before they're used.
This ensures that the master's TLS config has been registered with
the mysql driver before any connections are attempted.

This is the second part of resolving the following TLS verify
error:

2025-01-02 02:07:26 FATAL tls: failed to verify certificate: x509: certificate is valid for [old host], not [new host]
This ensures that the throttler's TLS config has been registered with
the mysql driver before any connections are attempted.

This is the second part of resolving the following TLS verify
error:

2025-01-02 02:07:26 FATAL tls: failed to verify certificate: x509: certificate is valid for [old host], not [new host]

@petervandoros petervandoros changed the title Pv/fix tls verify error Fix TKS verify error when gh-ost discovers the master server

Jan 3, 2025

@petervandoros petervandoros changed the title Fix TKS verify error when gh-ost discovers the master server Fix TLS verify error when gh-ost discovers the master server

Jan 3, 2025

@petervandoros petervandoros changed the title Fix TLS verify error when gh-ost discovers the master server Fix TLS verify error when gh-ost discovers the replication master

Jan 3, 2025

@meiji163

meiji163