Change:
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
Builds: kubernetes-e2e-gke-slow kubernetes-e2e-gke-test Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
Builds: kubernetes-e2e-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention...
[FLAKE-PING] This flaky-test issue would love to have more attention...
Removing attention-needed label. This is currently under investigation. Nothing here appears to be release blocking, but we will continue to reassess as we investigate.
Builds: kubernetes-e2e-gce-slow kubernetes-e2e-gke-slow kubernetes-soak-continuous-e2e-gke Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
Builds: kubernetes-e2e-gci-gce-slow kubernetes-e2e-gci-gke-slow-release-1.4 kubernetes-e2e-gci-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
any news wrt these failures?
Yes, investigated and discovered () which appears to indicate that these flakes are caused by . Tracking issue in
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
Great, thanks!
Builds: kubernetes-e2e-gci-gce-slow-release-1.4 kubernetes-e2e-gci-gke-prod kubernetes-e2e-gci-gke-slow-release-1.4 Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
Builds: kubernetes-e2e-gci-gce-slow-release-1.4 kubernetes-e2e-gci-gce-slow kubernetes-e2e-gci-gke-slow-release-1.4 kubernetes-e2e-gci-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
do you believe this is essentially a dup of , should this issue be closed?
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
They are different tests, but same root cause and solution. Let's leave them open until they are actually fixed.
Builds: kubernetes-e2e-gci-gce-slow-release-1.4 kubernetes-e2e-gci-gce-slow kubernetes-e2e-gci-gke-slow-release-1.4 kubernetes-e2e-gci-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
Builds: kubernetes-e2e-gci-gce-slow-release-1.4 kubernetes-e2e-gci-gke-slow-release-1.4 Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
This is a non-blocker for 1.5 This test calls directly to read value instead of through which contains . We should maybe move the retry logic from to ? cc who may want to fix this.
Builds: ci-kubernetes-e2e-gci-gce-slow-release-1.4 ci-kubernetes-e2e-gci-gke-slow-release-1.4 ci-kubernetes-e2e-gci-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
Builds: ci-kubernetes-e2e-gci-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
"VolumesInUse Status to NOT contain diskName" is a new failure mode we haven't seen in flakes before. can you see if there was a recent change that might've triggered that?
Investigated with Saad the failures "VolumesInUse Status to NOT contain diskName", looks like this happened during the PR was merged. Due to an error caused by this PR, mounter script will fail to garbage collect the rocket container. UnmountDevice will fail because the global mount has other mount references. After is reverted, this error should not happen again.
Builds: ci-kubernetes-e2e-gci-gce-slow-release-1.4 ci-kubernetes-e2e-gci-gce-slow ci-kubernetes-e2e-gci-gke-slow-release-1.4 ci-kubernetes-e2e-gci-gke-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
Builds: ci-kubernetes-e2e-gci-gce-slow-release-1.4 ci-kubernetes-e2e-gci-gce-slow Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
Builds: ci-kubernetes-e2e-gci-gke-slow ci-kubernetes-e2e-gke-containervm-1.3-gci-1.5-upgrade-cluster-new Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
Is it appropriate to move this to the next milestone? (and remove the non-release-blocker tag as well)
https://k8s- Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
Yep
Builds: ci-kubernetes-e2e-gci-gce-slow-release-1.4 ci-kubernetes-e2e-gci-gce-slow-release-1.5 ci-kubernetes-e2e-gci-gce-slow ci-kubernetes-e2e-gci-gke-slow-release-1.4 Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite}
CC
I'm working on a fix for this. It will change all the callers of kubectl exec in to use the retry wrapper instead.

Discussion:
framework.ExpectNoError(f.WaitForPodRunningSlow(host1Pod.Name)) <del> v, err := f.ReadFileViaContainer(host1Pod.Name, containerName, testFile) framework.ExpectNoError(err) framework.Logf("Read value: %v", v) Expect(strings.TrimSpace(v)).To(Equal(strings.TrimSpace(testFileContents))) </del> <ins> verifyPDContentsViaContainer(f, host1Pod.Name, containerName, map[string]string{testFile: testFileContents}) </ins> // Verify that disk is removed from node 1's VolumeInUse list framework.ExpectNoError(waitForPDInVolumesInUse(nodeClient, diskName, host0Name, nodeStatusTimeout, false /* shouldExist */))