Skip to content
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.

Sign up for GitHub

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

Jump to bottom

e2e script refactor broke ubernetes-lite e2e tests #21777

Closed
ghost opened this issue Feb 23, 2016 · 1 comment
Closed

e2e script refactor broke ubernetes-lite e2e tests #21777

ghost opened this issue Feb 23, 2016 · 1 comment
Labels
priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
v1.2

Comments

@ghost
Copy link

ghost commented Feb 23, 2016

#21524 broke ubernetes-lite e2e tests. PR to fix incoming.

Specifically:

kubernetes/hack/jenkins/job-configs/kubernetes-e2e.yaml

Line 159 in ac644e0

export KUBE_GCE_ZONE=""

setting KUBE_GCE_ZONE to an empty string causes it to be defaulted to (currently) "us-central1-b" rather than the zone in which the master components reside, leading to the following error:

2016/02/23 10:48:58 e2e.go:272: Running: Ginkgo tests
Setting up for KUBERNETES_PROVIDER="gce".
Project: k8s-jkns-e2e-gce-ubelite
Zone: us-central1-b
ERROR: (gcloud.compute.instances.describe) Could not fetch resource:
 - The resource 'projects/k8s-jkns-e2e-gce-ubelite/zones/us-central1-b/instances/jenkins-e2e-master' was not found

!!! Error in /jenkins-master-data/jobs/kubernetes-e2e-gce-ubernetes-lite/workspace/kubernetes/cluster/gce/util.sh:284
  'KUBE_MASTER_IP=$(gcloud compute instances describe --project "${PROJECT}" --zone "${ZONE}"       "${MASTER_NAME}" --fields networkInterfaces[0].accessConfigs[0].natIP       --format=text | awk '{ print $2 }')' exited with status 1
Call stack:
  1: /jenkins-master-data/jobs/kubernetes-e2e-gce-ubernetes-lite/workspace/kubernetes/cluster/gce/util.sh:284 detect-master(...)
  2: /jenkins-master-data/jobs/kubernetes-e2e-gce-ubernetes-lite/workspace/kubernetes/hack/ginkgo-e2e.sh:61 main(...)
Exiting with status 1
2016/02/23 10:48:59 e2e.go:278: Error running Ginkgo tests: exit status 1
@ghost ghost added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. team/control-plane labels Feb 23, 2016
@ghost ghost self-assigned this Feb 23, 2016
@ghost ghost added this to the v1.2 milestone Feb 23, 2016
@ghost
Copy link
Author

ghost commented Feb 23, 2016

@kubernetes/goog-testing @kubernetes/sig-testing @spxtr FYI

@ghost ghost mentioned this issue Feb 23, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
v1.2
Development

No branches or pull requests
0 participants