Skip to content

e2e Flake: Cluster failed to initialize within 300 seconds (possible metadata server issue?) #20916

Closed
@krousey

Description

10:12:14 Using master: e2e-scalability-master (external IP: 104.197.128.205)
10:12:14 Waiting up to 300 seconds for cluster initialization.
10:12:14 
10:12:14   This will continually check to see if the API for kubernetes is reachable.
10:12:14   This may time out if there was some uncaught error during start up.
10:12:14 
10:12:14 ......................................................................................................................................................Cluster failed to initialize within 300 seconds.
10:17:15 2016/02/09 10:17:15 e2e.go:309: Error running up: exit status 2
10:17:15 2016/02/09 10:17:15 e2e.go:305: Step 'up' finished in 8m0.913745413s

https://cloud.google.com/console/storage/kubernetes-jenkins/logs/kubernetes-e2e-gce-scalability/4496/

Metadata

Assignees

Labels

kind/flakeCategorizes issue or PR as related to a flaky test.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions