Skip to content

Failure cluster [3d2a4cbd...]: should report zero pinning counters after a fresh restart #118757

@pacoxu

Description

@pacoxu

Failure cluster 3d2a4cbd3657e98000ed

Error text:
[FAILED] Timed out after 60.001s.
Expected
    <string>: KubeletMetrics
to match keys: {
."kubelet_cpu_manager_pinning_requests_total"[]:
	Expected
	    <string>: Sample
	to match fields: {
	.Histogram:
		unexpected field Histogram: kubelet_cpu_manager_pinning_requests_total => 1 @[0]
	}
	
."kubelet_cpu_manager_pinning_errors_total"[]:
	Expected
	    <string>: Sample
	to match fields: {
	.Histogram:
		unexpected field Histogram: kubelet_cpu_manager_pinning_errors_total => 0 @[0]
	}
	
}
In [It] at: test/e2e_node/cpu_manager_metrics_test.go:158 @ 06/19/23 00:28:15.567

Recent failures:

2023/6/20 04:04:56 ci-kubernetes-node-kubelet-containerd-resource-managers
2023/6/20 00:04:56 ci-kubernetes-node-kubelet-containerd-resource-managers
2023/6/19 20:04:56 ci-kubernetes-node-kubelet-containerd-resource-managers
2023/6/19 16:04:55 ci-kubernetes-node-kubelet-containerd-resource-managers
2023/6/19 12:03:55 ci-kubernetes-node-kubelet-containerd-resource-managers

/kind failing-test

/sig node
similar to #118751 and is caused by #118752

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/nodeCategorizes an issue or PR as relevant to SIG Node.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions