-
Notifications
You must be signed in to change notification settings - Fork 40k
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.
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
integration flake: PersistentVolumeController could not update claim "default/fake-pvc" #26256
Comments
It turns out that volume integration tests have no logs at all, |
This flake affects also TestPersistentVolumeMultiPVs:
|
…hecks Automatic merge from submit-queue Add error checks to volume integration tests We need to know what's going on when a test fails, like in kubernetes#26256
Extended logging got merged just now, please post links to logs when it breaks again! |
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
Not blocking this on 1.3. |
It hasn't flaked for almost a month, can we close this? |
Closing this issue since previous fixes made the flake go away. |
PersistentVolume integration tests fail sometimes:
https://console.cltoud.google.com/storage/browser/kubernetes-jenkins/pr-logs/pull/26105/kubernetes-pull-test-unit-integration/27563/
There are some interesting reports in the log like:
Thans @quinton-hoole for report.
The text was updated successfully, but these errors were encountered: