Skip to content
This repository has been archived by the owner on Mar 19, 2022. It is now read-only.

FATAL: I cannot find /root/chef-solo/dna.json #279

Closed
iartarisi opened this issue Aug 28, 2013 · 4 comments · Fixed by #289
Closed

FATAL: I cannot find /root/chef-solo/dna.json #279

iartarisi opened this issue Aug 28, 2013 · 4 comments · Fixed by #289
Milestone

Comments

@iartarisi
Copy link

I just upgrade dot 0.3.0 and I get the above error doing knife solo cook. Where should I get that file from and where do I put it?

I can't find any documentation on this.

@tmatilai
Copy link
Collaborator

@mapleoin Sorry for the problems. :(

The file is generated in v0.3.0 based on your knife.rb configurations.
Could you please run the command with -VV option to get the debug output. Maybe that gives us a hint what the problem is.

The upgrade documentation is here.

@iartarisi
Copy link
Author

It turns out the chef-solo/dna.json file exists, but is a broken symbolic link.

My node file is a symbolic link so it seems it was copied to the target box unchanged. I think knife-solo should try to follow symbolic links when copying the node json file.

@tmatilai
Copy link
Collaborator

Ok, good that you found the root cause. I think I agree that symlinks should be followed. As windows doesn't even support them this would just unify the behavior. rsync for sure has many flags to choose from.

Anyway, as a special case, dna.json will anyway be generated if #275 and/or #232 are done.

tmatilai added a commit to tmatilai/knife-solo that referenced this issue Sep 22, 2013
Now that the directory structure on the node is not the same than
locally, the symlinks copied as is can result broken. So copy the
destination of the symlink.

Fixes matschaffer#279.
tmatilai added a commit to tmatilai/knife-solo that referenced this issue Sep 22, 2013
Now that the directory structure on the node is not the same than
locally, the symlinks copied as is can result broken. So copy the
destination of the symlink instead.

Fixes matschaffer#279.
@tmatilai
Copy link
Collaborator

PR #289 should fix this.

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

Successfully merging a pull request may close this issue.

2 participants