Skip to content

[sig-node] Summary API [NodeConformance] when querying /stats/summary ... networking info is nil on containerd #109082

@ehashman

Description

@ehashman

Failure cluster 79384df20f4e672ed9e1

Test: [sig-node] Summary API [NodeConformance] when querying /stats/summary should report resource usage through the stats api
Job:

  • ci-cgroup-systemd-containerd-node-e2e
  • ci-cos-containerd-node-e2e
  • pull-kubernetes-node-e2e-containerd
Error text:
test/e2e_node/summary_test.go:53
Timed out after 180.001s.
Expected
    <string>: Summary
to match fields: {
.Pods[summary-test-3122::stats-busybox-1].Network:
	Expected
	    <string>: NetworkStats
	to match fields: {
	[.InterfaceStats.Name:
		Expected
		    <string>: 
		to equal
		    <string>: eth0, .InterfaceStats.RxBytes:
		Expected
		    <*uint64 | 0x0>: nil
		not to be <nil>, .InterfaceStats.RxErrors:
		Expected
		    <*uint64 | 0x0>: nil
		not to be <nil>, .InterfaceStats.TxBytes:
		Expected
		    <*uint64 | 0x0>: nil
		not to be <nil>, .InterfaceStats.TxErrors:
		Expected
		    <*uint64 | 0x0>: nil
		not to be <nil>]
	.Interfaces:
		Expected
		    <[]v1alpha1.InterfaceStats | len:0, cap:0>: nil
		not to be nil
	}
	
}

test/e2e_node/summary_test.go:327

Recent failures:

3/27/2022, 9:20:16 AM ci-cgroup-systemd-containerd-node-e2e
3/27/2022, 3:20:08 AM ci-cos-containerd-node-e2e
3/26/2022, 9:20:08 PM ci-cos-containerd-node-e2e
3/26/2022, 4:06:12 AM ci-cos-containerd-node-e2e
3/25/2022, 11:58:17 AM ci-cos-containerd-node-e2e

Started flaking 03/23.

Screenshot at 2022-03-28 12-42-42
Screenshot at 2022-03-28 12-47-32
(second screenshot includes PRs)

/kind flake

/sig node

/priority important-soon
/milestone v1.24

Metadata

Metadata

Labels

help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/flakeCategorizes issue or PR as related to a flaky test.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.release-blockersig/nodeCategorizes an issue or PR as relevant to SIG Node.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions