kubernetes: duplicate metrics collector registration attempted
What happened:
The following error messages were found in the Kubernetes API server and controller manager logs:
E0423 17:35:58.491576 1 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.491625 1 prometheus.go:150] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.491901 1 prometheus.go:162] failed to register latency metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.492191 1 prometheus.go:174] failed to register work_duration metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.492367 1 prometheus.go:189] failed to register unfinished_work_seconds metric admission_quota_controller: duplicate metrics collector registration attempted
E0423 17:35:58.492507 1 prometheus.go:202] failed to register longest_running_processor_microseconds metric admission_quota_controller: duplicate metrics collector registration attempted
These appear to be for deprecated metrics (https://github.com/kubernetes/kubernetes/pull/71300) noted in https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.14.md.
What you expected to happen:
No duplicate metrics collector registration attempted
error messages in the API server or controller manager logs.
How to reproduce it (as minimally and precisely as possible):
Deploy a Kubernetes version 1.14 cluster and review API server or controller manager logs.
Anything else we need to know?:
No.
Environment:
- Kubernetes version (use
kubectl version
): 1.14.1 - Cloud provider or hardware configuration: IBM Cloud
- OS (e.g:
cat /etc/os-release
): Ubuntu 16.04.6 LTS - Kernel (e.g.
uname -a
): 4.4.0-145-generic - Install tools: Custom
- Network plugin and version (if this is a network-related bug): N/A
- Others: N/A
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 22 (8 by maintainers)
it fix in
v1.16
+