Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

integration flake: timed out while in waitForPersistentVolumePhase #26730

Closed
roberthbailey opened this issue Jun 2, 2016 · 4 comments · Fixed by #26894
Closed

integration flake: timed out while in waitForPersistentVolumePhase #26730

roberthbailey opened this issue Jun 2, 2016 · 4 comments · Fixed by #26894
Assignees
@jsafrane @spxtr
Labels
kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@roberthbailey
Copy link
Contributor

Test failed with panic: test timed out after 10m0s and the relevant part of the stack trace is:

goroutine 21070 [chan receive, 4 minutes]:
k8s.io/kubernetes/test/integration.waitForPersistentVolumePhase(0x7f26fa06d128, 0xc82de80c90, 0x27eb170, 0x9)
    /go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/integration/persistent_volumes_test.go:321 +0x6b
k8s.io/kubernetes/test/integration.TestPersistentVolumeRecycler(0xc8260a2360)
    /go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/integration/persistent_volumes_test.go:87 +0xb7a
testing.tRunner(0xc8260a2360, 0x3b14e78)
    /usr/local/go/src/testing/testing.go:473 +0x98
created by testing.RunTests
    /usr/local/go/src/testing/testing.go:582 +0x892

Logs: https://console.cloud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/25841/kubernetes-pull-test-unit-integration/28338/
@roberthbailey roberthbailey added the kind/flake Categorizes issue or PR as related to a flaky test. label Jun 2, 2016
@roberthbailey roberthbailey mentioned this issue Jun 2, 2016
Merged
@jsafrane
Copy link
Member

jsafrane commented Jun 3, 2016

@fejta (or anyone), integration tests do not log much and I don't know what's going on in volume controller. Would it be possible to raise integration test log level at least to v=3 (4 preferred)?

This was referenced Jun 6, 2016
Closed
Merged
@fejta
Copy link
Contributor

fejta commented Jun 6, 2016

@spxtr what is the status of kubernetes/test-infra#103?

@jsafrane
Copy link
Member

jsafrane commented Jun 7, 2016

@pmorie, can you please take a look?

@spxtr
Copy link
Contributor

spxtr commented Jun 7, 2016

Increasing integration log level can go into hack/test-integration.sh I think. It's probably a good idea to split them into their own job.

k8s-github-robot pushed a commit that referenced this issue Jun 13, 2016
Merge pull request #26894 from jsafrane/fix-integration-pv-flake
1ed5342 
Automatic merge from submit-queue

Fix integration pv flakes

There are two fixes in this PR:
- run tests in separarate functions and use objects with different names, otherwise events from the beginning of the function are caught later when we watch for events of a different PV/PVC
- don't set PV.Spec.ClaimRef.UID of pre-bound PVs. PVs with UID set are considered as bound and they are deleted/recycled when appropriate PVC does not exists yet.

Fixes #26730 and probably also ~~#26894~~ #26256
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsafrane jsafrane

@spxtr spxtr

Labels
kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix integration pv flakes jsafrane/kubernetes
5 participants
@fejta @jsafrane @a-robinson @spxtr @roberthbailey