tidb-operator: FailedScheduling: nodes didn't match node selector
Bug Report
What version of Kubernetes are you using?
Client Version: version.Info{Major:“1”, Minor:“13”, GitVersion:“v1.13.0”, GitCommit:“ddf47ac13c1a9483ea035a79cd7c10005ff21a6d”, GitTreeState:“clean”, BuildDate:“2018-12-03T21:04:45Z”, GoVersion:“go1.11.2”, Compiler:“gc”, Platform:“linux/amd64”} Server Version: version.Info{Major:“1”, Minor:“12”, GitVersion:“v1.12.5”, GitCommit:“51dd616cdd25d6ee22c83a858773b607328a18ec”, GitTreeState:“clean”, BuildDate:“2019-01-16T18:14:49Z”, GoVersion:“go1.10.7”, Compiler:“gc”, Platform:“linux/amd64”}
What version of TiDB Operator are you using?
TiDB Operator Version: version.Info{TiDBVersion:“2.1.0”, GitVersion:“v1.0.0-beta.2”, GitCommit:“bc913fc1459118c1d972be37e100d3a70a9e981a”, GitTreeState:“clean”, BuildDate:“2019-05-10T10:15:56Z”, GoVersion:“go1.12”, Compiler:“gc”, Platform:“linux/amd64”}
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
NAME PROVISIONER AGE local-storage kubernetes.io/no-provisioner 5m40s
What’s the status of the TiDB cluster pods?
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE demo-discovery-58fb7c6765-wwgbx 1/1 Running 0 3m4s 10.244.1.5 kube-node-3 <none> demo-monitor-5ddb4bf8c-9xv96 2/2 Running 0 3m4s 10.244.2.4 kube-node-1 <none> demo-pd-0 0/1 Pending 0 3m4s <none> <none> <none> demo-pd-1 0/1 Pending 0 3m4s <none> <none> <none> demo-pd-2 0/1 Pending 0 3m4s <none> <none> <none>
What did you do?
Following the guide (https://github.com/pingcap/tidb-operator/blob/master/docs/local-dind-tutorial.md) to deploy a TiDB cluster in the DinD Kubernetes cluster.
What did you expect to see? Success to deploy a TiDB cluster in the DinD Kubernetes cluster
What did you see instead? pd’s status stucks in pending. When I run “kubectl describe po -n <ns> <pod-name>”, I see the following warning: Warning FailedScheduling 2m45s (x2510 over 7m45s) tidb-scheduler 0/4 nodes are available: 4 node(s) didn’t match node selector.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (9 by maintainers)
pingcap/tidb-operator:latest
works fine. Thanks!