Miquel Torres Barceló

Is a node which cannot resolve its own hostname in a useful state at all? What is happening is that the distro name is set to "sudo: unable to resolve...

We could do that, then examine stderr, and if it's not empty we abort. Problem would be if it is a warning going to stdout.

The problem is caused by upload_template having two phases: - using `put()` to upload the file to the user's _home_ directory - using `sudo` to move the file to its...

Committed a partial fix (Ugly error still appears), and filed a bug in fabric (fabric/fabric#629), needed to be able to fix it more nicely on our side. Will leave this...

Thanks @gondoi , I hope the LittleChef 1.5.0 release today fixes your issue.

Mmm, I cannot think of a non-hacky way of implementing a chef-resume. An alternative would be to catch the fabric error, then _ask_ whether it should continue or not...

You assumption is correct, though this cookbook's case is a bit confusing. There are a couple of cookbooks that use `node.save`, at which point the current node attributes (well, everything)...

In any case I marked this issue as "enhancement". We can add a list of cookbooks that use `node.save` to the documentation so that users are aware of which cookbooks...

The exact same problem happened to us. The problem is that the ability to pin the Chef version depends greatly on what distribution you use and on what deployment method...

Why does it have to do with a server being barebone? Do you mean that you want to use `deploy_chef` to install Chef for the first time on a server?...