-
Notifications
You must be signed in to change notification settings - Fork 235
-
Notifications
You must be signed in to change notification settings - Fork 235
mysql-agent can't recreate MySQL Cluster after full k8s cluster restart #83
Comments
We are facing the same issue, @gites did you find something useful ? |
Hi @paolomainardi, I’m ironing out the last few issues with the upgrade of the operator to MySQL 8 which will fix the issue (see #87 for details). In the meantime you may be able to rectify the situation on your existing cluster by |
ok thanks a lot @prydie |
@prydie I did a test build from commit a0d35f4 and cluster is still failing after restrat, but now due to bad SSL settings.
Attaching logs from pods below: agent0.log |
Hey @gites, yeah, we decided to merge the MySQL 8 change with that still outstanding as complete disaster recovery was already broken. I'm taking a look at it today. I'll update here once I've got something working 🙂. |
BUG REPORT
Versions
MySQL Operator Version:
0.1.0
Environment:
kubectl version
):Cloud provider or hardware configuration:
minikube
OS (e.g. from /etc/os-release):
Buildroot 2017.11
Kernel (e.g.
uname -a
):Linux minikube 4.9.64 #1 SMP Fri Mar 30 21:27:22 UTC 2018 x86_64 GNU/Linux
Others:
What happened?
Mysql-agent can't recreate MySQL Cluster after full k8s restart (the VM runing one node k8s was restarted)
What you expected to happen?
MySQL Cluster should have been recreated by mysql-agent
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
The text was updated successfully, but these errors were encountered: