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

[BUG]dataprotection crash #8159

Closed
ahjing99 opened this issue Sep 18, 2024 · 0 comments · Fixed by #8160
Closed

[BUG]dataprotection crash #8159

ahjing99 opened this issue Sep 18, 2024 · 0 comments · Fixed by #8160
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@ahjing99
Copy link
Collaborator

➜ ~ kbcli version
Kubernetes: v1.30.3-gke.1639000
KubeBlocks: 1.0.0-alpha.6
kbcli: 1.0.0-alpha.0

➜  ~ k get pod -n kb-system
NAME                                            READY   STATUS             RESTARTS        AGE
kb-addon-snapshot-controller-557f9cf454-9bxhg   1/1     Running            0               39m
kubeblocks-756c8fbc7d-xh9c7                     1/1     Running            0               39m
kubeblocks-dataprotection-7d47dc6f6c-zv4kh      0/1     CrashLoopBackOff   12 (3m6s ago)   39m
➜  ~ k logs kubeblocks-dataprotection-7d47dc6f6c-zv4kh  -n kb-system
Defaulted container "dataprotection" out of: dataprotection, tools (init)
2024-09-18T07:44:46.769Z	INFO	setup	config file: /etc/kubeblocks/config.yaml
2024-09-18T07:44:46.769Z	INFO	setup	config settings: map[cert_dir:/tmp/k8s-webhook-server/serving-certs cm_namespace:kb-system cm_recon_retry_duration_ms:1000 data_plane_affinity:{"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"preference":{"matchExpressions":[{"key":"kb-data","operator":"In","values":["true"]}]},"weight":100}]}} data_plane_tolerations:[{"effect":"NoSchedule","key":"kb-data","operator":"Equal","value":"true"}] dataprotection_reconcile_workers:4 default_storage_class:kb-default-sc exec_worker_service_account_name:kubeblocks-dataprotection-exec-worker gc_frequency_seconds:3600 health_probe_bind_address::8081 kubeblocks_serviceaccount_name:kubeblocks kubeblocks_tools_image:docker.io/apecloud/kubeblocks-tools:1.0.0-alpha.6 kubeconfig: kubernetes_cluster_domain:cluster.local leader_elect:true leader_elect_id:abd03fda managed_namespaces: metrics_bind_address::8080 multi_cluster_contexts: multi_cluster_contexts_disabled: multi_cluster_kubeconfig: user_agent:kubeblocks volumesnapshot_api_beta:false worker_cluster_role_name:kubeblocks-dataprotection-worker-role worker_service_account_annotations:{} worker_service_account_name:kubeblocks-dataprotection-worker zap_devel:false zap_encoder:console zap_log_level: zap_stacktrace_level: zap_time_encoding:iso8601]
2024-09-18T07:44:46.771Z	ERROR	setup	unable to start manager	{"error": "no kind is registered for the type v1.Cluster in scheme \"pkg/runtime/scheme.go:100\""}
main.main
	/src/cmd/dataprotection/main.go:243
runtime.main
	/usr/local/go/src/runtime/proc.go:267
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants