You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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:
node_name
tolocalhost
, which appears to be what chef-client (or perhaps just the guest OS) defaults tonode_name
a required attributeThe text was updated successfully, but these errors were encountered: