Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind bug
/kind feature
What happened:
This looks like a problem with the automated testing. See https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/60065/pull-kubernetes-kubemark-e2e-gce/81204?log#log for an example. Note the entry
W0313 10:25:15.700] 2018/03/13 10:25:15 process.go:150: Running: ./test/kubemark/stop-kubemark.sh
W0313 10:25:17.378] ERROR: (gcloud.compute.instances.delete) Could not fetch resource:
W0313 10:25:17.378] - The resource 'projects/k8s-jkns-pr-kubemark/zones/us-central1-f/instances/e2e-81204-kubemark-master' was not found
and others like it.
What you expected to happen:
I expected the GCE resource wrangling to not fail.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version): release-1.8
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a):
- Install tools:
- Others:
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
This looks like a problem with the automated testing. See https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/60065/pull-kubernetes-kubemark-e2e-gce/81204?log#log for an example. Note the entry
and others like it.
What you expected to happen:
I expected the GCE resource wrangling to not fail.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version): release-1.8uname -a):