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.

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

GCE if you set more zones that instances kops creates InstanceGroupManager with size 0 #3293

Closed
chrislovecnm opened this issue Aug 28, 2017 · 5 comments
Labels
area/gce lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@chrislovecnm
Copy link
Contributor

chrislovecnm commented Aug 28, 2017

On master right now:

$ kops version
Version 1.7.1-beta.1 (git-90edd15be)

I am getting the following error:

I0827 22:39:10.575840   89700 executor.go:157] Executing task "InstanceGroupManager/us-east1-d-nodes-clove-gce-k8s-vorstella-com": *gcetasks.InstanceGroupManager {"Name":"us-east1-d-nodes-clove-gce-k8s-vorstella-com","Lifecycle":"Sync","Zone":"us-east1-d","BaseInstanceName":"nodes","InstanceTemplate":{"Name":"nodes-clove-gce-k8s-vorstella-com","Lifecycle":"Sync","Network":{"Name":"default","Lifecycle":"Sync","CIDR":"172.20.0.0/16"},"Tags":["clove-gce-k8s-vorstella-com-k8s-io-role-node"],"Preemptible":false,"BootDiskImage":"cos-cloud/cos-stable-57-9202-64-0","BootDiskSizeGB":100,"BootDiskType":"pd-standard","CanIPForward":true,"Subnet":null,"Scopes":["compute-rw","monitoring","logging-write","storage-ro"],"Metadata":{"cluster-name":{"Name":"","Resource":"clove.gce.k8s.vorstella.com"},"startup-script":{"Name":"","Resource":{}}},"MachineType":"n1-standard-2","ID":"nodes-clove-gce-k8s-vorstella-com-1503895121"},"TargetSize":0,"TargetPools":null}
W0827 22:39:10.897452   89700 executor.go:109] error running task "InstanceGroupManager/us-east1-d-nodes-clove-gce-k8s-vorstella-com" (9m35s remaining to succeed): error creating InstanceGroupManager: googleapi: Error 400: Required field 'resource.targetSize' not specified, required
I0827 22:39:10.897482   89700 executor.go:124] No progress made, sleeping before retrying 1 failed task(s)
I0827 22:39:20.900675   89700 executor.go:91] Tasks: 43 done / 44 total; 1 can run
I0827 22:39:20.900776   89700 executor.go:157] Executing task "InstanceGroupManager/us-east1-d-nodes-clove-gce-k8s-vorstella-com": *gcetasks.InstanceGroupManager {"Name":"us-east1-d-nodes-clove-gce-k8s-vorstella-com","Lifecycle":"Sync","Zone":"us-east1-d","BaseInstanceName":"nodes","InstanceTemplate":{"Name":"nodes-clove-gce-k8s-vorstella-com","Lifecycle":"Sync","Network":{"Name":"default","Lifecycle":"Sync","CIDR":"172.20.0.0/16"},"Tags":["clove-gce-k8s-vorstella-com-k8s-io-role-node"],"Preemptible":false,"BootDiskImage":"cos-cloud/cos-stable-57-9202-64-0","BootDiskSizeGB":100,"BootDiskType":"pd-standard","CanIPForward":true,"Subnet":null,"Scopes":["compute-rw","monitoring","logging-write","storage-ro"],"Metadata":{"cluster-name":{"Name":"","Resource":"clove.gce.k8s.vorstella.com"},"startup-script":{"Name":"","Resource":{}}},"MachineType":"n1-standard-2","ID":"nodes-clove-gce-k8s-vorstella-com-1503895121"},"TargetSize":0,"TargetPools":null}
W0827 22:39:21.230276   89700 executor.go:109] error running task "InstanceGroupManager/us-east1-d-nodes-clove-gce-k8s-vorstella-com" (9m24s remaining to succeed): error creating InstanceGroupManager: googleapi: Error 400: Required field 'resource.targetSize' not specified, required
I0827 22:39:21.230294   89700 executor.go:124] No progress made, sleeping before retrying 1 failed task(s)

Notice:

"TargetSize":0

Command I am running

kops create cluster $KOPS_SERVER \
	--zones $ZONES \
	--master-zones "us-east1-c" \
	--project $PROJECT \
	--yes \
	-v 10 |& tee /tmp/debug.out

adding --node-count does not help.

@chrislovecnm
Copy link
Contributor Author

/area gce

@chrislovecnm chrislovecnm changed the title GCE seems to be broken in master GCE if you set more zones that instances kops creates InstanceGroupManager with size 0 Aug 28, 2017
@chrislovecnm
Copy link
Contributor Author

The problem is that --zones was set to 3 zones, and we only had two nodes. We need to ensure that zones is smaller or equal to number of nodes.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 3, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 8, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gce lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants