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

Packer fails when missing node_name #1118

Closed
bklang opened this issue May 3, 2014 · 1 comment
Closed

Packer fails when missing node_name #1118

bklang opened this issue May 3, 2014 · 1 comment

Comments

@bklang
Copy link

bklang commented May 3, 2014

This is following up on #1100.

The field node_name is described as "optional", though the build fails without it because knife is unable to remove the chef client from the chef server after a successful configuration run. This results in the VM being destroyed.

I can think of a couple of ways to address this, but I'm not sure which you prefer:

  • Set the default node_name to localhost, which appears to be what chef-client (or perhaps just the guest OS) defaults to
  • Alternatively (and this is probably safer) make node_name a required attribute
@bklang bklang changed the title Documentation problem on required attributes for Chef Client Packer fails when optional attribute missing from Chef Client provisioner May 8, 2014
@sethvargo sethvargo changed the title Packer fails when optional attribute missing from Chef Client provisioner Packer fails when missing node_name Feb 24, 2015
@mitchellh
Copy link
Contributor

I think this is a dup of #1295. This should get fixed with that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants