Check master replication fails when running the cluster the first time

[XaratosS]

Hello,

we ran into the following issue: When we ran your mysql role, the replication didnt work on the slave on the first run. We had to do a second run and then the replication started without any issues.

Following happend: The Check master replication status is being checked before the replication on the slave is being configured. I think, that you the Slave replication status should be checked a second time before you start the replication.

Is it possible to fix it myself and get a merge into this role?

with kind regards.

[XaratosS]

Also I do have another question. Is there a reason, why you create the databases empy on both servers? The replication dosnt work with newly created databases on the master. The databases will not be created on the slave.

[lipanpan-hub]

Hello,

we ran into the following issue: When we ran your mysql role, the replication didnt work on the slave on the first run. We had to do a second run and then the replication started without any issues.

Following happend: The Check master replication status is being checked before the replication on the slave is being configured. I think, that you the Slave replication status should be checked a second time before you start the replication.

Is it possible to fix it myself and get a merge into this role?

with kind regards.

I have exactly the same question

[XaratosS]

Also I do have another question. Is there a reason, why you create the databases empy on both servers? The replication dosnt work with newly created databases on the master. The databases will not be created on the slave.

You can ignore this one. This was a fail on my side. I forgot to set up the replication variable.

[github-actions[bot]]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

[github-actions[bot]]

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.