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

AWS: Don't try to create an ELB if we end up with no subnets #21993

Closed
justinsb opened this issue Feb 25, 2016 · 1 comment · Fixed by #22064
Closed

AWS: Don't try to create an ELB if we end up with no subnets #21993

justinsb opened this issue Feb 25, 2016 · 1 comment · Fixed by #22064
Assignees
@justinsb
Labels
priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Milestone
v1.2

Comments

@justinsb
Copy link
Member

User reported an error (when using a private ELB, but we can avoid this anyway)...

 start-kube-controller-manager.sh[7244]: I0225 16:26:39.740004    7244 aws_loadbalancer.go:65] Creating load balancer for kube-system/monitoring-grafana with name: %!(EXTRA string=a2653f816d6ec11e59363064e140b16c)
Feb 25 16:26:39 ip-10-50-185-151 start-kube-controller-manager.sh[7244]: W0225 16:26:39.740130    7244 retry_handler.go:55] Inserting delay before AWS request (elasticloadbalancing::CreateLoadBalancer) to avoid RequestLimitExceeded: 6s
Feb 25 16:26:39 ip-10-50-185-151 start-kube-controller-manager.sh[7244]: E0225 16:26:39.937525    7244 servicecontroller.go:188] Failed to process service delta. Retrying: Failed to create load balancer for service default/jenkins: ValidationError: Either AvailabilityZones or SubnetIds must be specified
@justinsb justinsb added this to the v1.2 milestone Feb 26, 2016
@justinsb justinsb added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Feb 26, 2016
@justinsb justinsb self-assigned this Mar 4, 2016
@justinsb
Copy link
Member Author

justinsb commented Mar 4, 2016

Will be fixed by #22064

@justinsb justinsb mentioned this issue Mar 4, 2016
Merged
justinsb added a commit to justinsb/kubernetes that referenced this issue Mar 6, 2016
@justinsb
AWS: If we have no subnets, bail out early
02e79b9 
We know the ELB call will fail, so we error out early rather than
hitting the API.  Preserves rate limit quota, and also allows us to give
a more self-evident message.

Fix kubernetes#21993
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this issue Feb 20, 2019
@k8s-publishing-bot
Merge pull request kubernetes#21993 from enxebre/openshift-machine-ap…
549895d 
…i-namespace

Update protected OpenShift namespaces: openshift-machine-api

Origin-commit: 888322d77ed7aebd6389cd257d2c528d2774ce76
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justinsb justinsb

Labels
priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Milestone
v1.2
Development

Successfully merging a pull request may close this issue.

AWS: Fix problems identifying subnets for internal ELBs justinsb/kubernetes
2 participants
@justinsb @saad-ali