[chef] Re: knife node changes and client run concurrency

[Jesse Campbell < >]

In my org we avoid putting anything in the node, preferring to have controlled attributes in roles, environments, and recipes.

This would likely be a significant change to your workflow, but it has worked well for us thus far.

-Jesse

On Fri, Mar 8, 2013 at 3:25 AM, Martin Eigenbrodt < " target="_blank"> > wrote:

Hi there,

i experienced the following problem: A CI Job ran "knife node from file .." but the node attributes seemed to be unchanged later. Investigating erchefs Log I found out, that there had been an concurrent chef-client run on the relevant node.
It looks like the client read the node data before the run, while it run knife has updated the data and after the run the client pushed  its old node - and know wrong - data back to the server.

Is this a known issue? How can I guard against this?


Regards,

Martin