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

kubelet panics on instances without public IP (AWS) #9123

Closed
antoineco opened this issue Jun 2, 2015 · 3 comments
Closed

kubelet panics on instances without public IP (AWS) #9123

antoineco opened this issue Jun 2, 2015 · 3 comments
Labels
area/cloudprovider priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@antoineco
Copy link
Contributor

Since node auto-registration was introduced in v0.18.0, the kubelet crashes on AWS if the instance it runs on doesn't have a public IP.

The full error trace is available here: https://gist.github.com/antoineco/8d5a168aae8ab5b94cef
@dchen1107 dchen1107 added sig/node Categorizes an issue or PR as relevant to SIG Node. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 2, 2015
@dchen1107
Copy link
Member

cc/ @roberthbailey

@roberthbailey
Copy link
Contributor

The kubelet asks the cloud provider for node addresses, and the implementation is specific to each provider. It looks like this is a bug in the aws cloud provider: the stack trace points to line 412 of aws.go.

justinsb added a commit to justinsb/kubernetes that referenced this issue Jun 3, 2015
@justinsb
Avoid nil-pointer dereference panics in AWS
e3eb23f 
These were introduced because the new official AWS SDK uses *string
where the old library used strings.  We now use the helpers much
more (orEmpty and isNilOrEmpty).

Fixes kubernetes#9123
@justinsb justinsb mentioned this issue Jun 3, 2015
Merged
@justinsb
Copy link
Member

justinsb commented Jun 3, 2015

Thanks for the great bug report. Working on a fix in #9189.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/cloudprovider priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@justinsb @antoineco @dchen1107 @roberthbailey