-
-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New cluster doesn't happen to end up in orchestrator #673
Comments
Same problem |
Yes and logs in orchestrator show - Unable to determine cluster name This is for a brand new cluster |
deployed the cluster in a different namespace and also tried in same namespace as operator, same result. |
I have a similar issue: the cluster starts, but after some time the mysql becomes non-ready and I get the above log message in the operator logs. |
I have this problem too |
Same problem |
Please make sure you are not hitting #170. (see https://www.bitpoke.io/docs/mysql-operator/deploy-mysql-cluster/#note-1). Also please try with v0.5.0. |
Hello. In my case:
EVERYTHING WORKED, BUT there were errors in MySQL clusters only.Obviously, I figured the problem was mysql-operator - no changes helped at all. Everything worked, but MySQL clusters gradually stopped working. Horror... RUN Kubespray upgrade-cluster.ymlAn error occurred - not deleted pod with MySQL cluster. The same error was at the very beginning when I tried to fix the cluster K8S. I ignored her then. This happened at the stage "Drain node"
Kubespray unable to upgrade the cluster completely - in my case that was the reason. Solution (in my case)
|
hello same problem here. 77 clusters deployed without problem but one of them does not want to deploy the second node because "cluster not found in Orchestrator". No other error at all
|
hello, I found that some data are still in the sqlite db after days of cluster deletion. in database_instance_last_analysis , database_instance_tls, kv_store, hostname_ips.
thx for your help, I'm really stuck here :( |
Cluster is stuck in Ready: False phase because mysql pod never gets Ready.
The text was updated successfully, but these errors were encountered: