[k8s.io] Services should work after restarting apiserver [Disruptive] {Kubernetes e2e suite}

[k8s-github-robot]

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging/6072/

Failed: [k8s.io] Services should work after restarting apiserver [Disruptive] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:369
Jun 29 17:42:31.753: error restarting apiserver: error running gcloud [container clusters --project=k8s-jkns-e2e-gke-staging --zone=us-central1-f upgrade jenkins-e2e --master --cluster-version=1.3.0-beta.2 --quiet]; got error exit status 1, stdout "<ClusterUpdate\n desiredLocations: []\n desiredMasterVersion: '1.3.0-beta.2'>\n", stderr "ERROR: (gcloud.container.clusters.upgrade) ResponseError: code=400, message=Cluster master can only be upgraded to the latest (default) version. This does not upgrade the nodes..\n"

[bprashanth]

This is

sion=1.3.0-beta.2 --quiet]; got error exit status 1, stdout "<ClusterUpdate\n desiredLocations: []\n desiredMasterVersion: '1.3.0-beta.2'>\n", stderr "ERROR: (gcloud.container.clusters.upgrade) ResponseError: code=400, message=Cluster master can only be upgraded to the latest (default) version

duping into #27011

[j3ffml]

I see what happened. This cluster was launched at version 1.3.0-beta.2, which was the default in staging for testing. Then in the middle of the e2e run, the server-side default version was changed back to 1.2.5, which prompted the above rejection. We don't often do beta version testing in staging, but I'll add this project to the whitelist anyway.