Skip to content

data race in nodeshutdown tests #110854

@kerthcet

Description

@kerthcet

Which jobs are flaking?

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/110768/pull-kubernetes-unit/1541991414412349440

WARNING: DATA RACE
Read at 0x00c0004c1703 by goroutine 96:
  testing.(*common).logDepth()
      /usr/local/go/src/testing/testing.go:882 +0x4ce
  testing.(*common).log()
      /usr/local/go/src/testing/testing.go:869 +0x84
  testing.(*common).Log()
      /usr/local/go/src/testing/testing.go:910 +0x58
  testing.(*T).Log()
      <autogenerated>:1 +0x55
  k8s.io/kubernetes/vendor/k8s.io/klog/v2/ktesting.(*tlogger).log()
      /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/ktesting/testinglogger.go:279 +0x524
  k8s.io/kubernetes/vendor/k8s.io/klog/v2/ktesting.(*tlogger).Info()
      /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/klog/v2/ktesting/testinglogger.go:250 +0x157
  k8s.io/kubernetes/vendor/github.com/go-logr/logr.Logger.Info()
      /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/go-logr/logr/logr.go:261 +0xe3
  k8s.io/kubernetes/pkg/kubelet/nodeshutdown.(*managerImpl).processShutdownEvent.func3()
      /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/nodeshutdown/nodeshutdown_manager_linux.go:386 +0x7e4
  k8s.io/kubernetes/pkg/kubelet/nodeshutdown.(*managerImpl).processShutdownEvent.func5()
      /home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/pkg/kubelet/nodeshutdown/nodeshutdown_manager_linux.go:388 +0x9d
Previous write at 0x00c0004c1703 by goroutine 8:
  testing.tRunner.func1()
      /usr/local/go/src/testing/testing.go:1426 +0x7af
  runtime.deferreturn()
      /usr/local/go/src/runtime/panic.go:436 +0x32
  testing.(*T).Run.func1()
      /usr/local/go/src/testing/testing.go:1486 +0x47

Which tests are flaking?

TestLocalStorage in pkg/kubelet/nodeshutdown

Since when has it been flaking?

N/A

Testgrid link

No response

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Relevant SIG(s)

/sig node

Metadata

Metadata

Assignees

Labels

kind/flakeCategorizes issue or PR as related to a flaky test.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.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