Skip to content

TestKMSProvider is flaky #60614

New issue
Jump to bottom
New issue
Jump to bottom
Closed
Closed
TestKMSProvider is flaky#60614
Assignees
mikedanese
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.kind/flakeCategorizes issue or PR as related to a flaky test.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.sig/authCategorizes an issue or PR as relevant to SIG Auth.
@liggitt

Description

@liggitt
liggitt
opened on Mar 1, 2018

TestKMSProvider is flaking slightly in head:

https://storage.googleapis.com/k8s-gubernator/triage/index.html?test=TestKMSProvider

--- FAIL: TestKMSProvider (10.47s)
	testserver.go:106: Starting kube-apiserver on port 37352...
	testserver.go:118: Waiting for /healthz to be ok...
	kms_transformation_test.go:109: failed to get DEK from KMS: timed-out while getting encryption request from KMS Plugin Mock

The timeout block is suspect:

kubernetes/test/integration/master/kms_transformation_test.go

Lines 140 to 147 in 07240b7

func getDEKFromKMSPlugin(pluginMock *base64Plugin) ([]byte, error) {
select {
case e := <-pluginMock.encryptRequest:
return e.Plain, nil
case <-time.After(1 * time.Microsecond):
return nil, fmt.Errorf("timed-out while getting encryption request from KMS Plugin Mock")
}
}

If this is asynchronous, 1 ms is a super tight tolerance for an integration test. looking at the test, though, it's unclear which piece would be asynchronous.

Metadata

Assignees

Labels

kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.kind/flakeCategorizes issue or PR as related to a flaky test.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.sig/authCategorizes an issue or PR as relevant to SIG Auth.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions