- 03 Feb, 2016 10 commits
-
-
Tim Hockin authored
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Jeff Lowdermilk authored
Revert "remove cluster logging e2e test from flaky suite"
-
Jeff Lowdermilk authored
skip update when deleting with grace-period=0
-
Jeff Lowdermilk authored
Mark L7 tests as Feature:Ingress
-
Jeff Lowdermilk authored
Update docs on flaky issues
-
Jeff Lowdermilk authored
Make HPA Deployment tests [Feature:Deployment] until GKE has enabled them
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Jeff Lowdermilk authored
Add timeout, fix potential startup hang
-
Chao Xu authored
-
- 02 Feb, 2016 30 commits
-
-
Minhan Xia authored
-
Jeff Lowdermilk authored
Reference #20015 for [Flaky] NodeOutOfDisk tests
-
Minhan Xia authored
explictly check log tainted string
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Jeff Lowdermilk authored
Un-disable "Pods should get a host IP" e2e.
-
Jeff Lowdermilk authored
Promote DaemonRestart e2es out of Flaky
-
Jeff Lowdermilk authored
Adjust the limits in the kubelet resource tracking test
-
Saad Ali authored
Fix a couple typos
-
Chao Xu authored
-
Paul Morie authored
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
CJ Cullen authored
Also add a test for the Update() logic. Reordered tunnels vs. storage initialization (prevent a nil ptr panic)
-
Jeff Lowdermilk authored
Don't re-check with gcloud for a firewall's existence to fix a potential flake.
-
Jeff Lowdermilk authored
Change docker health checker to using `docker ps`
-
David Oppenheimer authored
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Yu-Ju Hong authored
`docker ps` is a more reliable health check than docker version from past experiences.
-
Jeff Lowdermilk authored
Add timestamps to the liveness e2e test
-
Chao Xu authored
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Jeff Lowdermilk authored
Knock down the timeouts for gce, gce-slow, gke, and gke-slow
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
k8s-merge-robot authored
Auto commit by PR queue bot
-
Jan Safranek authored
Add a mutex to guard SetUpAt() and TearDownAt() calls - they should not run in parallel. There is a race in these calls when there are two pods using the same volume, one of them is dying and the other one starting. TearDownAt() checks that a volume is not needed by any pods and detaches the volume. It does so by counting how many times is the volume mounted (GetMountRefs() call below). When SetUpAt() of the starting pod already attached the volume and did not mount it yet, TearDownAt() of the dying pod will detach it - GetMountRefs() does not count with this volume. These two threads run in parallel: dying pod.TearDownAt("myVolume") starting pod.SetUpAt("myVolume") | | | AttachDisk("myVolume") refs, err := mount.GetMountRefs() | Unmount("myDir") | if refs == 1 { | | | Mount("myVolume", "myDir") | | | | DetachDisk("myVolume") | | start containers - OOPS! The volume is detached! | finish the pod cleanup Also, add some logs to cinder plugin for easier debugging in the future, add a test and update the fake mounter to know about bind mounts.
-