-
Notifications
You must be signed in to change notification settings - Fork 498
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
Minor usability issue when you try to restore from a scheduled backup #634
Comments
@shinnosuke-okada We have removed the long pod name from the scheduled backup dir in this PR: #576 https://github.com/pingcap/tidb-operator/pull/576/files#diff-87269cdf14e9a2fb6ca87a9e728057a5R7 Could you use the latest |
@weekface Is it possible to make the latest helm charts available via
|
You can probably change the helm repository to instead point to this github repo or your local folder. It is also always possible to run helm install as a local-exec. You can also disable the helm provisioner part in the terraform and do the helm install manually for now. There is definitely a problem with flexibly selecting the proper version. I opened an issue for this: #640 |
Thanks @gregwebs! Yes, I was actually trying to upgrade from a local dir but it somehow failed. After that, terraform can neither fix nor destroy so I'm currently redeploying a fresh cluster. I'll post the result as soon as I have it ready. Thanks. |
Sorry, we are currently making terraform changes that are not backwards-compatible. I am pushing towards us having proper usage as a module. After that there are more possibilities for dealing with terraform changes. |
Sounds good. No problem - I understand it's a WIP :) Just a quick update. I deployed with the latest code from master branch but scheduled backup is hitting a segmentation fault. Also, I cannot ssh into the bastion node for some reason.
|
I will take a look at the bastion issue. @LinuxGit Can you take a look at the segmentation fault listed above? |
@shinnosuke-okada I've submitted a new issue #643. |
The |
Checked out the latest master and merged my changes today. I somehow ended up with an incomplete cluster.
Will investigate further tomorrow. Thanks. |
The deployment of tidb-operator failed for some reason, could you please provide the output of “helm ls” and “kubectl get po -n tidb-admin”? |
@aylei Looks like this:
|
@shinnosuke-okada It turns out the chart of |
Did your merge change this
|
Oh yes, you're right - it was a careless mistake on my end. Sorry, and thank you! Let me quickly verify this issue again. |
Verified with the latest master that the scheduled backup name is short enough. For example: Thanks everyone! |
Bug Report
What version of Kubernetes are you using?
What version of TiDB Operator are you using?
latest master
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
terraform apply
fromdeploy/aws
What did you expect to see?
Restore to work according to the doc without any error.
What did you see instead?
Seems like we're hitting the character limit. The scheduled backup name should probably be shortened.
Workaround
Copy the content of scheduled backup to a new folder with shorter name.
The text was updated successfully, but these errors were encountered: