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

GKE e2e tests are failing to come up #52045

Closed
ericchiang opened this issue Sep 6, 2017 · 9 comments
Closed

GKE e2e tests are failing to come up #52045

ericchiang opened this issue Sep 6, 2017 · 9 comments
Assignees
@zmerlynn
Labels
area/test-infra kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-blocker sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Milestone
v1.8

Comments

@ericchiang
Copy link
Contributor

ericchiang commented Sep 6, 2017 •
edited by zmerlynn
Loading

Master release blocking e2e tests are currently failing to come up. For example:
https://k8s-testgrid.appspot.com/release-master-blocking#gke

GCE tests are fine.

cc @kubernetes/test-infra-maintainers
cc @spxtr (current testinfra on call)
cc @kubernetes/kubernetes-release-managers
@ericchiang ericchiang added area/test-infra kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-blocker sig/testing Categorizes an issue or PR as relevant to SIG Testing. team/gke labels Sep 6, 2017
@ericchiang ericchiang added this to the v1.8 milestone Sep 6, 2017
@k8s-github-robot
Copy link

[MILESTONENOTIFIER] Milestone Labels Complete

@ericchiang

Issue label settings:

  • sig/testing: Issue will be escalated to these SIGs if needed.
  • priority/critical-urgent: Never automatically move out of a release milestone; continually escalate to contributor and SIG through all available channels.
  • kind/bug: Fixes a bug discovered during the current release.
Additional instructions available here

@zmerlynn
Copy link
Member

zmerlynn commented Sep 6, 2017

/assign

@zmerlynn
Copy link
Member

zmerlynn commented Sep 6, 2017

I've got an internal fix out for this that's being deployed imminently.

@krzyzacy
Copy link
Member

krzyzacy commented Sep 6, 2017

cc @abgworrall

@zmerlynn
Copy link
Member

zmerlynn commented Sep 6, 2017

I'm not clear why the top comment says "GCI tests are fine." gke-gci is just as red. (FWIW, this was injected by #51816 because one of the pods we deploy on masters was using the old init-containers notation.)

@abgworrall
Copy link
Contributor

abgworrall commented Sep 6, 2017 •
edited
Loading

@zmerlynn , I've interpreted that as 'non-GKE tests are unaffected by this issue'.

@ericchiang
Copy link
Contributor Author

@zmerlynn yes, sorry I meant pure gce tests. (too many initialisms)

@zmerlynn
Copy link
Member

zmerlynn commented Sep 6, 2017

Up went green: https://k8s-testgrid.appspot.com/google-gke#gke. Closing!

@zmerlynn zmerlynn closed this as completed Sep 6, 2017
@roberthbailey
Copy link
Contributor

Thanks for jumping on this @zmerlynn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zmerlynn zmerlynn

Labels
area/test-infra kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-blocker sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
v1.8
Development

No branches or pull requests
6 participants
@krzyzacy @ericchiang @zmerlynn @roberthbailey @abgworrall @k8s-github-robot