Exiting littlechef shortly after a deploy creates permission denied error

[Eddy Hernandez]

I exited a deploy a few seconds after I ran fix node:myserver and now I get the issues described over here https://github.com/tobami/littlechef/issues/91

Specifying the roles manually still works, like "fix node:myserver role:base" etc.

Is there anything I can do to resolve this without rebuilding and rerunning the recipes for this machine? Either change permissions on a directory/file or add this manually? 

Also, this has happened on more than one occasion.

[Miquel Torres]

OK, there were a couple of fixes to this, it shouldn't be happening anymore.
Are you using LittleChef 1.5.1 with fabric 1.5.4?

> --
> You received this message because you are subscribed to the Google Groups
> "littlechef" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to littlechef+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Eddy Hernandez]

I am using:

LittleChef 1.5.1

Fabric 1.5.4

Paramiko 1.10.0

[Miquel Torres]

OK, and which error message do you get, exactly?

On Thu, Jun 20, 2013 at 1:49 PM, Eddy Hernandez

[Eddy Hernandez]

Here's what I get, (I just replaced my site name and ip)

(chef)± fix node:sitename.com

== Configuring sitename.com ==

Fatal error: put() encountered an exception while uploading '<StringIO.StringIO instance at 0x10a23b3b0>'

Underlying exception:

    Permission denied

Aborting.

Fatal error: Failed to upload '/etc/chef/solo.rb'

This can happen when the deployment user does not have a home directory, which is needed as a temporary location

Aborting.

Disconnecting from 123.123.123.123:1313... done.