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

Set nodeName to internal DNS by default for ec2 #1170

Closed
dak1n1 opened this issue Jan 12, 2016 · 0 comments · Fixed by #1310
Closed

Set nodeName to internal DNS by default for ec2 #1170

dak1n1 opened this issue Jan 12, 2016 · 0 comments · Fixed by #1310

Comments

@dak1n1
Copy link
Contributor

dak1n1 commented Jan 12, 2016

The openshift-ansible installer currently creates node-config.yaml using the internal IP as the nodeName. This causes the following error when a node is configured for AWS.

Jan 12 12:39:18 ip-172-20-1-226.ec2.internal atomic-openshift-node[32871]: E0112 12:39:18.979571 32871 kubelet.go:925] Unable to construct api.Node object for kubelet: failed to get external ID from cloud provider: instance not found

Instead, the nodeName should be set to the internal DNS name of the host. For example:

nodeName: ip-172-20-1-226.ec2.internal
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix hostname for aws cloud provider detiber/openshift-ansible
1 participant
@dak1n1