WhatBrokeToday
FAQ
Today's Trends
minorInvestigatingKubernetes

Kubernetes apiserver cacher DATA RACE in integration tests

  1. Investigating(current)
  2. Trending(upcoming)
  3. Workaround available(upcoming)
  4. Resolved(upcoming)

Executive summary

A data race was detected in the Kubernetes apiserver cacher during test integration runs on master (TestGenerateName).

No verified workaround yet

None of the linked reports describe a mitigation. Follow this incident to hear when one appears.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    apiserver cacher DATA RACE(opens GitHub issue in a new tab)

    What happened? https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-integration-race-master/2119963182406569984 [sig-api-machinery] k8s.io/kubernetes/test/integration/apiserver: apidefinitions expand_less 1m48s {Failed === RUN TestGenerateName testserver.go:708: Resolved testserver package path to: "/home/prow/go/src/k8s.io/kubernetes/cmd/kube-apiserver/app/testing" testserver.go:471: runtime-config=map[api/all:true] testserver.go:472: Starting kube-apiserver on port 42331...…

    by pohly 0upvotes 3comments

Timeline

  1. First report on GitHub issue

    apiserver cacher DATA RACE

    Source