Skip to content
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

TidbMonitor pods failed to be created when using CR #1825

Closed
weekface opened this issue Feb 28, 2020 · 1 comment · Fixed by #1834
Closed

TidbMonitor pods failed to be created when using CR #1825

weekface opened this issue Feb 28, 2020 · 1 comment · Fixed by #1834
Labels
type/bug Something isn't working

Comments

@weekface
Copy link
Contributor

I create TiDB cluster using this command:

$ kubectl apply -f example/basic/

The TidbMonitor pod failed to be created, here is the tidb-controller-manager logs:

E0228 08:24:26.730170       1 tidb_monitor_controller.go:118] TidbMonitor: default/basic, sync failed, err: tidbcluster.pingcap.com "basic" not found
I0228 08:24:26.730689       1 event.go:255] Event(v1.ObjectReference{Kind:"TidbMonitor", Namespace:"default", Name:"basic", UID:"29b31a69-9b34-4fe6-8ea2-6140059b6058", APIVersion:"pingcap.com/v1alpha1", ResourceVersion:"50293", FieldPath:""}): type: 'Warning' reason: 'FailedSync' Sync TidbMonitor[default/basic] Deployment failed,err:tidbcluster.pingcap.com "basic" not found
@weekface weekface added the type/bug Something isn't working label Feb 28, 2020
@Yisaer
Copy link
Contributor

Yisaer commented Feb 29, 2020

This is a bug, the tidbmonitor is supposed to use its namespace when the targetRef namespace is not defined.

ref:
#1834

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
2 participants