Problem: When using the foreman-installer to install a fresh katello scenario with an external database, the installer fails during DB migrations.
When using a dump of a local installation (also without data; directly after foreman-installer) on the target database server, the installer is capable to migrate over the existing data and use the external database server.
It also creates some tables which indicates that there is no permission problem.
Expected outcome: Installer migrates and seeds the database successfully
Foreman and Proxy versions: Foreman 2.0 / Katello 3.15 / PostgresDB 10 or 11 / otherwise defaults from Installer
Foreman and Proxy plugin versions: Defaults from installer
After some trial and error it seems like this problem is the result of high network latency to the database.
If I use the exact same configuration for Azure Datebases for Postgres but use a location near to the Foreman VM (with latency of about 8ms), the migration works fine. As soon as the latency to the database is relatively high (about ~80ms), the migrations fail.
So I’m wondering if a fix is even needed? Assuming a high network latency, the performance would be bad anyway…